tenth. Then transfer to the corresponding spoke in the Software Test Engineering Scorecard on the second next page of the Self-Assessment.
Your completed Software Test Engineering Scorecard will give you a clear presentation of which Software Test Engineering areas need attention.
Software Test Engineering
Scorecard Example
Example of how the finalized Scorecard can look like:
Software Test Engineering
Scorecard
Your Scores:
BEGINNING OF THE
SELF-ASSESSMENT:
Table of Contents
About The Art of Service8
Included Resources - how to access8
Purpose of this Self-Assessment10
How to use the Self-Assessment11
Software Test Engineering
Scorecard Example13
Software Test Engineering
Scorecard14
BEGINNING OF THE
SELF-ASSESSMENT:15
CRITERION #1: RECOGNIZE16
CRITERION #2: DEFINE:28
CRITERION #3: MEASURE:44
CRITERION #4: ANALYZE:60
CRITERION #5: IMPROVE:76
CRITERION #6: CONTROL:92
CRITERION #7: SUSTAIN:105
Software Test Engineering and Managing Projects, Criteria for Project Managers:130
1.0 Initiating Process Group: Software Test Engineering131
1.1 Project Charter: Software Test Engineering133
1.2 Stakeholder Register: Software Test Engineering135
1.3 Stakeholder Analysis Matrix: Software Test Engineering136
2.0 Planning Process Group: Software Test Engineering138
2.1 Project Management Plan: Software Test Engineering140
2.2 Scope Management Plan: Software Test Engineering142
2.3 Requirements Management Plan: Software Test Engineering144
2.4 Requirements Documentation: Software Test Engineering146
2.5 Requirements Traceability Matrix: Software Test Engineering148
2.6 Project Scope Statement: Software Test Engineering150
2.7 Assumption and Constraint Log: Software Test Engineering152
2.8 Work Breakdown Structure: Software Test Engineering154
2.9 WBS Dictionary: Software Test Engineering156
2.10 Schedule Management Plan: Software Test Engineering158
2.11 Activity List: Software Test Engineering160
2.12 Activity Attributes: Software Test Engineering162
2.13 Milestone List: Software Test Engineering164
2.14 Network Diagram: Software Test Engineering166
2.15 Activity Resource Requirements: Software Test Engineering168
2.16 Resource Breakdown Structure: Software Test Engineering169
2.17 Activity Duration Estimates: Software Test Engineering171
2.18 Duration Estimating Worksheet: Software Test Engineering174
2.19 Project Schedule: Software Test Engineering176
2.20 Cost Management Plan: Software Test Engineering178
2.21 Activity Cost Estimates: Software Test Engineering180
2.22 Cost Estimating Worksheet: Software Test Engineering182
2.23 Cost Baseline: Software Test Engineering184
2.24 Quality Management Plan: Software Test Engineering186
2.25 Quality Metrics: Software Test Engineering188
2.26 Process Improvement Plan: Software Test Engineering190
2.27 Responsibility Assignment Matrix: Software Test Engineering192
2.28 Roles and Responsibilities: Software Test Engineering194
2.29 Human Resource Management Plan: Software Test Engineering196
2.30 Communications Management Plan: Software Test Engineering198
2.31 Risk Management Plan: Software Test Engineering200
2.32 Risk Register: Software Test Engineering202
2.33 Probability and Impact Assessment: Software Test Engineering204
2.34 Probability and Impact Matrix: Software Test Engineering206
2.35 Risk Data Sheet: Software Test Engineering208
2.36 Procurement Management Plan: Software Test Engineering210
2.37 Source Selection Criteria: Software Test Engineering212
2.38 Stakeholder Management Plan: Software Test Engineering214
2.39 Change Management Plan: Software Test Engineering216
3.0 Executing Process Group: Software Test Engineering218
3.1 Team Member Status Report: Software Test Engineering220
3.2 Change Request: Software Test Engineering222
3.3 Change Log: Software Test Engineering224
3.4 Decision Log: Software Test Engineering226
3.5 Quality Audit: Software Test Engineering228
3.6 Team Directory: Software Test Engineering231
3.7 Team Operating Agreement: Software Test Engineering233
3.8 Team Performance Assessment: Software Test Engineering235
3.9 Team Member Performance Assessment: Software Test Engineering237
3.10 Issue Log: Software Test Engineering239
4.0 Monitoring and Controlling Process Group: Software Test Engineering241
4.1 Project Performance Report: Software Test Engineering243
4.2 Variance Analysis: Software Test Engineering245
4.3 Earned Value Status: Software Test Engineering247
4.4 Risk Audit: Software Test Engineering249
4.5 Contractor Status Report: Software Test Engineering251
4.6 Formal Acceptance: Software Test Engineering253
5.0 Closing Process Group: Software Test Engineering255
5.1 Procurement Audit: Software Test Engineering257
5.2 Contract Close-Out: Software Test Engineering259
5.3 Project or Phase Close-Out: Software Test Engineering261
5.4 Lessons Learned: Software Test Engineering263
Index265
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