Software Contract A Complete Guide - 2020 Edition. Gerardus Blokdyk
Scorecard on the second next page of the Self-Assessment.
Your completed Software Contract Scorecard will give you a clear presentation of which Software Contract areas need attention.
Software Contract
Scorecard Example
Example of how the finalized Scorecard can look like:
Software Contract
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 Contract
Scorecard Example12
Software Contract
Scorecard13
BEGINNING OF THE
SELF-ASSESSMENT:14
CRITERION #1: RECOGNIZE15
CRITERION #2: DEFINE:26
CRITERION #3: MEASURE:42
CRITERION #4: ANALYZE:57
CRITERION #5: IMPROVE:73
CRITERION #6: CONTROL:89
CRITERION #7: SUSTAIN:101
Software Contract and Managing Projects, Criteria for Project Managers:126
1.0 Initiating Process Group: Software Contract127
1.1 Project Charter: Software Contract129
1.2 Stakeholder Register: Software Contract131
1.3 Stakeholder Analysis Matrix: Software Contract132
2.0 Planning Process Group: Software Contract134
2.1 Project Management Plan: Software Contract136
2.2 Scope Management Plan: Software Contract138
2.3 Requirements Management Plan: Software Contract140
2.4 Requirements Documentation: Software Contract142
2.5 Requirements Traceability Matrix: Software Contract144
2.6 Project Scope Statement: Software Contract146
2.7 Assumption and Constraint Log: Software Contract148
2.8 Work Breakdown Structure: Software Contract150
2.9 WBS Dictionary: Software Contract152
2.10 Schedule Management Plan: Software Contract155
2.11 Activity List: Software Contract157
2.12 Activity Attributes: Software Contract159
2.13 Milestone List: Software Contract161
2.14 Network Diagram: Software Contract163
2.15 Activity Resource Requirements: Software Contract165
2.16 Resource Breakdown Structure: Software Contract167
2.17 Activity Duration Estimates: Software Contract169
2.18 Duration Estimating Worksheet: Software Contract171
2.19 Project Schedule: Software Contract173
2.20 Cost Management Plan: Software Contract175
2.21 Activity Cost Estimates: Software Contract177
2.22 Cost Estimating Worksheet: Software Contract179
2.23 Cost Baseline: Software Contract181
2.24 Quality Management Plan: Software Contract183
2.25 Quality Metrics: Software Contract185
2.26 Process Improvement Plan: Software Contract187
2.27 Responsibility Assignment Matrix: Software Contract189
2.28 Roles and Responsibilities: Software Contract191
2.29 Human Resource Management Plan: Software Contract193
2.30 Communications Management Plan: Software Contract195
2.31 Risk Management Plan: Software Contract197
2.32 Risk Register: Software Contract199
2.33 Probability and Impact Assessment: Software Contract201
2.34 Probability and Impact Matrix: Software Contract203
2.35 Risk Data Sheet: Software Contract205
2.36 Procurement Management Plan: Software Contract207
2.37 Source Selection Criteria: Software Contract209
2.38 Stakeholder Management Plan: Software Contract211
2.39 Change Management Plan: Software Contract213
3.0 Executing Process Group: Software Contract215
3.1 Team Member Status Report: Software Contract217
3.2 Change Request: Software Contract219
3.3 Change Log: Software Contract221
3.4 Decision Log: Software Contract223
3.5 Quality Audit: Software Contract225
3.6 Team Directory: Software Contract228
3.7 Team Operating Agreement: Software Contract230
3.8 Team Performance Assessment: Software Contract232
3.9 Team Member Performance Assessment: Software Contract234
3.10 Issue Log: Software Contract236
4.0 Monitoring and Controlling Process Group: Software Contract238
4.1 Project Performance Report: Software Contract240
4.2 Variance Analysis: Software Contract242
4.3 Earned Value Status: Software Contract244
4.4 Risk Audit: Software Contract246
4.5 Contractor Status Report: Software Contract248
4.6 Formal Acceptance: Software Contract250
5.0 Closing Process Group: Software Contract252
5.1 Procurement Audit: Software Contract254
5.2 Contract Close-Out: Software Contract256
5.3 Project or Phase Close-Out: Software Contract258
5.4 Lessons Learned: Software Contract260
Index262
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. Do you need different information or graphics?
<--- Score
2. Which needs are not included or involved?
<--- Score
3. What do employees need