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 Agile Software Scorecard on the second next page of the Self-Assessment.
Your completed Agile Software Scorecard will give you a clear presentation of which Agile Software areas need attention.
Agile Software
Scorecard Example
Example of how the finalized Scorecard can look like:
Agile Software
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
Agile Software
Scorecard Example12
Agile Software
Scorecard13
BEGINNING OF THE
SELF-ASSESSMENT:14
CRITERION #1: RECOGNIZE15
CRITERION #2: DEFINE:21
CRITERION #3: MEASURE:33
CRITERION #4: ANALYZE:41
CRITERION #5: IMPROVE:52
CRITERION #6: CONTROL:81
CRITERION #7: SUSTAIN:90
Agile Software and Managing Projects, Criteria for Project Managers:120
1.0 Initiating Process Group: Agile Software121
1.1 Project Charter: Agile Software123
1.2 Stakeholder Register: Agile Software125
1.3 Stakeholder Analysis Matrix: Agile Software126
2.0 Planning Process Group: Agile Software128
2.1 Project Management Plan: Agile Software131
2.2 Scope Management Plan: Agile Software133
2.3 Requirements Management Plan: Agile Software135
2.4 Requirements Documentation: Agile Software138
2.5 Requirements Traceability Matrix: Agile Software140
2.6 Project Scope Statement: Agile Software142
2.7 Assumption and Constraint Log: Agile Software144
2.8 Work Breakdown Structure: Agile Software146
2.9 WBS Dictionary: Agile Software148
2.10 Schedule Management Plan: Agile Software151
2.11 Activity List: Agile Software153
2.12 Activity Attributes: Agile Software155
2.13 Milestone List: Agile Software157
2.14 Network Diagram: Agile Software159
2.15 Activity Resource Requirements: Agile Software161
2.16 Resource Breakdown Structure: Agile Software163
2.17 Activity Duration Estimates: Agile Software165
2.18 Duration Estimating Worksheet: Agile Software167
2.19 Project Schedule: Agile Software169
2.20 Cost Management Plan: Agile Software171
2.21 Activity Cost Estimates: Agile Software173
2.22 Cost Estimating Worksheet: Agile Software175
2.23 Cost Baseline: Agile Software177
2.24 Quality Management Plan: Agile Software179
2.25 Quality Metrics: Agile Software181
2.26 Process Improvement Plan: Agile Software183
2.27 Responsibility Assignment Matrix: Agile Software185
2.28 Roles and Responsibilities: Agile Software187
2.29 Human Resource Management Plan: Agile Software189
2.30 Communications Management Plan: Agile Software191
2.31 Risk Management Plan: Agile Software193
2.32 Risk Register: Agile Software195
2.33 Probability and Impact Assessment: Agile Software197
2.34 Probability and Impact Matrix: Agile Software199
2.35 Risk Data Sheet: Agile Software201
2.36 Procurement Management Plan: Agile Software203
2.37 Source Selection Criteria: Agile Software205
2.38 Stakeholder Management Plan: Agile Software207
2.39 Change Management Plan: Agile Software209
3.0 Executing Process Group: Agile Software211
3.1 Team Member Status Report: Agile Software213
3.2 Change Request:
