answer to this question is clearly defined’.
There are two ways in which you can choose to interpret this statement;
1.how aware are you that the answer to the question is clearly defined
2.for more in-depth analysis you can choose to gather evidence and confirm the answer to the question. This obviously will take more time, most Self-Assessment users opt for the first way to interpret the question and dig deeper later on based on the outcome of the overall Self-Assessment.
A score of ‘1’ would mean that the answer is not clear at all, where a ‘5’ would mean the answer is crystal clear and defined. Leave emtpy when the question is not applicable or you don’t want to answer it, you can skip it without affecting your score. Write your score in the space provided.
After you have responded to all the appropriate statements in each section, compute your average score for that section, using the formula provided, and round to the nearest tenth. Then transfer to the corresponding spoke in the Software Reliability Scorecard on the second next page of the Self-Assessment.
Your completed Software Reliability Scorecard will give you a clear presentation of which Software Reliability areas need attention.
Software Reliability
Scorecard Example
Example of how the finalized Scorecard can look like:
Software Reliability
Scorecard
Your Scores:
BEGINNING OF THE
SELF-ASSESSMENT:
Table of Contents
About The Art of Service7
Included Resources - how to access7
Purpose of this Self-Assessment9
How to use the Self-Assessment10
Software Reliability
Scorecard Example12
Software Reliability
Scorecard13
BEGINNING OF THE
SELF-ASSESSMENT:14
CRITERION #1: RECOGNIZE15
CRITERION #2: DEFINE:27
CRITERION #3: MEASURE:43
CRITERION #4: ANALYZE:57
CRITERION #5: IMPROVE:72
CRITERION #6: CONTROL:88
CRITERION #7: SUSTAIN:100
Software Reliability and Managing Projects, Criteria for Project Managers:125
1.0 Initiating Process Group: Software Reliability126
1.1 Project Charter: Software Reliability128
1.2 Stakeholder Register: Software Reliability130
1.3 Stakeholder Analysis Matrix: Software Reliability131
2.0 Planning Process Group: Software Reliability133
2.1 Project Management Plan: Software Reliability135
2.2 Scope Management Plan: Software Reliability137
2.3 Requirements Management Plan: Software Reliability139
2.4 Requirements Documentation: Software Reliability141
2.5 Requirements Traceability Matrix: Software Reliability143
2.6 Project Scope Statement: Software Reliability145
2.7 Assumption and Constraint Log: Software Reliability147
2.8 Work Breakdown Structure: Software Reliability149
2.9 WBS Dictionary: Software Reliability151
2.10 Schedule Management Plan: Software Reliability154
2.11 Activity List: Software Reliability156
2.12 Activity Attributes: Software Reliability158
2.13 Milestone List: Software Reliability160
2.14 Network Diagram: Software Reliability162
2.15 Activity Resource Requirements: Software Reliability164
2.16 Resource Breakdown Structure: Software Reliability165
2.17 Activity Duration Estimates: Software Reliability167
2.18 Duration Estimating Worksheet: Software Reliability169
2.19 Project Schedule: Software Reliability171
2.20 Cost Management Plan: Software Reliability173
2.21 Activity Cost Estimates: Software Reliability175
2.22 Cost Estimating Worksheet: Software Reliability177
2.23 Cost Baseline: Software Reliability179
2.24 Quality Management Plan: Software Reliability181
2.25 Quality Metrics: Software Reliability183
2.26 Process Improvement Plan: Software Reliability185
2.27 Responsibility Assignment Matrix: Software Reliability187
2.28 Roles and Responsibilities: Software Reliability189
2.29 Human Resource Management Plan: Software Reliability191
2.30 Communications Management Plan: Software Reliability193
2.31 Risk Management Plan: Software Reliability195
2.32 Risk Register: Software Reliability197
2.33 Probability and Impact Assessment: Software Reliability199
2.34 Probability and Impact Matrix: Software Reliability201
2.35 Risk Data Sheet: Software Reliability203
2.36 Procurement Management Plan: Software Reliability205
2.37 Source Selection Criteria: Software Reliability207
2.38 Stakeholder Management Plan: Software Reliability209
2.39 Change
