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 Management Plan: Software Reliability211
3.0 Executing Process Group: Software Reliability213
3.1 Team Member Status Report: Software Reliability215
3.2 Change Request: Software Reliability217
3.3 Change Log: Software Reliability219
3.4 Decision Log: Software Reliability221
3.5 Quality Audit: Software Reliability223
3.6 Team Directory: Software Reliability226
3.7 Team Operating Agreement: Software Reliability228
3.8 Team Performance Assessment: Software Reliability230
3.9 Team Member Performance Assessment: Software Reliability232
3.10 Issue Log: Software Reliability234
4.0 Monitoring and Controlling Process Group: Software Reliability236
4.1 Project Performance Report: Software Reliability238
4.2 Variance Analysis: Software Reliability240
4.3 Earned Value Status: Software Reliability242
4.4 Risk Audit: Software Reliability244
4.5 Contractor Status Report: Software Reliability246
4.6 Formal Acceptance: Software Reliability248
5.0 Closing Process Group: Software Reliability250
5.1 Procurement Audit: Software Reliability252
5.2 Contract Close-Out: Software Reliability255
5.3 Project or Phase Close-Out: Software Reliability257
5.4 Lessons Learned: Software Reliability259
Index261
CRITERION #1: RECOGNIZE
INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Where do you need to exercise leadership?
<---