style="font-size:15px;"> the 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 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
