Plan: System Design Review217
3.0 Executing Process Group: System Design Review219
3.1 Team Member Status Report: System Design Review221
3.2 Change Request: System Design Review223
3.3 Change Log: System Design Review225
3.4 Decision Log: System Design Review227
3.5 Quality Audit: System Design Review229
3.6 Team Directory: System Design Review232
3.7 Team Operating Agreement: System Design Review234
3.8 Team Performance Assessment: System Design Review236
3.9 Team Member Performance Assessment: System Design Review238
3.10 Issue Log: System Design Review240
4.0 Monitoring and Controlling Process Group: System Design Review242
4.1 Project Performance Report: System Design Review244
4.2 Variance Analysis: System Design Review246
4.3 Earned Value Status: System Design Review248
4.4 Risk Audit: System Design Review250
4.5 Contractor Status Report: System Design Review252
4.6 Formal Acceptance: System Design Review254
5.0 Closing Process Group: System Design Review256
5.1 Procurement Audit: System Design Review258
5.2 Contract Close-Out: System Design Review260
5.3 Project or Phase Close-Out: System Design Review262
5.4 Lessons Learned: System Design Review264
Index266
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. Is it needed?
<--- Score
2. How much are sponsors, customers, partners, stakeholders involved in System Design Review? In other words, what are the risks, if System Design Review does not deliver successfully?
<--- Score
3. What tools and technologies are needed for a custom System Design Review project?
<--- Score
4. What extra resources will you need?
<--- Score
5. What is the System Design Review problem definition? What do you need to resolve?
<--- Score
6. How are training requirements identified?
<--- Score
7. What else needs to be measured?
<--- Score
8. To what extent does each concerned units management team recognize System Design Review as an effective investment?
<--- Score
9. What resources or support might you need?
<--- Score
10. What is the problem or issue?
<--- Score
11. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
12. How are the System Design Review’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
13. What are the clients issues and concerns?
<--- Score
14. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
15. Does your organization need more System Design Review education?
<--- Score
16. To what extent would your organization benefit from being recognized as a award recipient?
<--- Score
17. Who needs budgets?
<--- Score
18. Who else hopes to benefit from it?
<--- Score
19. What are the expected benefits of System Design Review to the stakeholder?
<--- Score
20. How do you recognize an objection?
<--- Score
21. What System Design Review coordination do you need?
<--- Score
22. Who needs to know?
<--- Score
23. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
24. Will System Design Review deliverables need to be tested and, if so, by whom?
<--- Score
25. What System Design Review problem should be solved?
<--- Score
26. Do you need different information or graphics?
<--- Score
27. What needs to stay?
<--- Score
28. Do you need to avoid or amend any System Design Review activities?
<--- Score
29.
