Senior Software Engineer A Complete Guide - 2020 Edition. Gerardus Blokdyk
Then transfer to the corresponding spoke in the Senior Software Engineer Scorecard on the second next page of the Self-Assessment.
Your completed Senior Software Engineer Scorecard will give you a clear presentation of which Senior Software Engineer areas need attention.
Senior Software Engineer
Scorecard Example
Example of how the finalized Scorecard can look like:
Senior Software Engineer
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
Senior Software Engineer
Scorecard Example13
Senior Software Engineer
Scorecard14
BEGINNING OF THE
SELF-ASSESSMENT:15
CRITERION #1: RECOGNIZE16
CRITERION #2: DEFINE:28
CRITERION #3: MEASURE:45
CRITERION #4: ANALYZE:60
CRITERION #5: IMPROVE:77
CRITERION #6: CONTROL:94
CRITERION #7: SUSTAIN:106
Senior Software Engineer and Managing Projects, Criteria for Project Managers:131
1.0 Initiating Process Group: Senior Software Engineer132
1.1 Project Charter: Senior Software Engineer134
1.2 Stakeholder Register: Senior Software Engineer136
1.3 Stakeholder Analysis Matrix: Senior Software Engineer137
2.0 Planning Process Group: Senior Software Engineer139
2.1 Project Management Plan: Senior Software Engineer142
2.2 Scope Management Plan: Senior Software Engineer144
2.3 Requirements Management Plan: Senior Software Engineer146
2.4 Requirements Documentation: Senior Software Engineer148
2.5 Requirements Traceability Matrix: Senior Software Engineer150
2.6 Project Scope Statement: Senior Software Engineer152
2.7 Assumption and Constraint Log: Senior Software Engineer154
2.8 Work Breakdown Structure: Senior Software Engineer156
2.9 WBS Dictionary: Senior Software Engineer158
2.10 Schedule Management Plan: Senior Software Engineer161
2.11 Activity List: Senior Software Engineer163
2.12 Activity Attributes: Senior Software Engineer165
2.13 Milestone List: Senior Software Engineer167
2.14 Network Diagram: Senior Software Engineer169
2.15 Activity Resource Requirements: Senior Software Engineer171
2.16 Resource Breakdown Structure: Senior Software Engineer173
2.17 Activity Duration Estimates: Senior Software Engineer175
2.18 Duration Estimating Worksheet: Senior Software Engineer177
2.19 Project Schedule: Senior Software Engineer179
2.20 Cost Management Plan: Senior Software Engineer181
2.21 Activity Cost Estimates: Senior Software Engineer183
2.22 Cost Estimating Worksheet: Senior Software Engineer185
2.23 Cost Baseline: Senior Software Engineer187
2.24 Quality Management Plan: Senior Software Engineer189
2.25 Quality Metrics: Senior Software Engineer191
2.26 Process Improvement Plan: Senior Software Engineer193
2.27 Responsibility Assignment Matrix: Senior Software Engineer195
2.28 Roles and Responsibilities: Senior Software Engineer197
2.29 Human Resource Management Plan: Senior Software Engineer199
2.30 Communications Management Plan: Senior Software Engineer201
2.31 Risk Management Plan: Senior Software Engineer203
2.32 Risk Register: Senior Software Engineer205
2.33 Probability and Impact Assessment: Senior Software Engineer207
2.34 Probability and Impact Matrix: Senior Software Engineer209
2.35 Risk Data Sheet: Senior Software Engineer211
2.36 Procurement Management Plan: Senior Software Engineer213
2.37 Source Selection Criteria: Senior Software Engineer215
2.38 Stakeholder Management Plan: Senior Software Engineer217
2.39 Change Management Plan: Senior Software Engineer219
3.0 Executing Process Group: Senior Software Engineer221
3.1 Team Member Status Report: Senior Software Engineer223
3.2 Change Request: Senior Software Engineer225
3.3 Change Log: Senior Software Engineer227
3.4 Decision Log: Senior Software Engineer229
3.5 Quality Audit: Senior Software Engineer231
3.6 Team Directory: Senior Software Engineer234
3.7 Team Operating Agreement: Senior Software Engineer236
3.8 Team Performance Assessment: Senior Software Engineer238
3.9 Team Member Performance Assessment: Senior Software Engineer240
3.10 Issue Log: Senior Software Engineer242
4.0 Monitoring and Controlling Process Group: Senior Software Engineer244
4.1 Project Performance Report: Senior Software Engineer246
4.2 Variance Analysis: Senior Software Engineer248
4.3 Earned Value Status: Senior Software Engineer250
4.4 Risk Audit: Senior Software Engineer252
4.5 Contractor Status Report: Senior Software Engineer254
4.6 Formal Acceptance: Senior Software Engineer256
5.0 Closing Process Group: Senior Software Engineer258
5.1 Procurement Audit: Senior Software Engineer260
5.2 Contract Close-Out: Senior Software Engineer262
5.3 Project or Phase Close-Out: Senior Software Engineer264
5.4 Lessons Learned: Senior Software Engineer266
Index268
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