Closed Systems215
3.3 Change Log: Closed Systems217
3.4 Decision Log: Closed Systems219
3.5 Quality Audit: Closed Systems221
3.6 Team Directory: Closed Systems224
3.7 Team Operating Agreement: Closed Systems226
3.8 Team Performance Assessment: Closed Systems228
3.9 Team Member Performance Assessment: Closed Systems231
3.10 Issue Log: Closed Systems233
4.0 Monitoring and Controlling Process Group: Closed Systems235
4.1 Project Performance Report: Closed Systems237
4.2 Variance Analysis: Closed Systems239
4.3 Earned Value Status: Closed Systems241
4.4 Risk Audit: Closed Systems243
4.5 Contractor Status Report: Closed Systems245
4.6 Formal Acceptance: Closed Systems247
5.0 Closing Process Group: Closed Systems249
5.1 Procurement Audit: Closed Systems251
5.2 Contract Close-Out: Closed Systems253
5.3 Project or Phase Close-Out: Closed Systems255
5.4 Lessons Learned: Closed Systems257
Index259
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. Have you identified your Closed systems key performance indicators?
<--- Score
2. Are there any revenue recognition issues?
<--- Score
3. Are there any specific expectations or concerns about the Closed systems team, Closed systems itself?
<--- Score
4. Can management personnel recognize the monetary benefit of Closed systems?
<--- Score
5. What do you need to start doing?
<--- Score
6. Will new equipment/products be required to facilitate Closed systems delivery, for example is new software needed?
<--- Score
7. Does Closed systems create potential expectations in other areas that need to be recognized and considered?
<--- Score
8. How do you identify subcontractor relationships?
<--- Score
9. What is the problem and/or vulnerability?
<--- Score
10. What do employees need in the short term?
<--- Score
11. Whom do you really need or want to serve?
<--- Score
12. Who needs to know?
<--- Score
13. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
14. For your Closed systems project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
15. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
16. Who defines the rules in relation to any given issue?
<--- Score
17. How are the Closed systems’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
18. Will Closed systems deliverables need to be tested and, if so, by whom?
<--- Score
19. What activities does the governance board need to consider?
<--- Score
20. Who needs budgets?
<--- Score
21. Do you need different information or graphics?
<--- Score
22. What information do users need?
<--- Score
23. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
24. Will it solve real problems?
<--- Score
25. What needs to stay?
<--- Score
26. Do you need to avoid or amend any Closed systems activities?
<--- Score
27. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?
<--- Score
28. What tools and technologies are needed for a custom Closed systems project?
<--- Score
29. Are controls defined to recognize and contain problems?
<--- Score
30. How do you recognize an objection?
<---
