3.2 Change Request: Systems Assurance220
3.3 Change Log: Systems Assurance222
3.4 Decision Log: Systems Assurance224
3.5 Quality Audit: Systems Assurance226
3.6 Team Directory: Systems Assurance229
3.7 Team Operating Agreement: Systems Assurance231
3.8 Team Performance Assessment: Systems Assurance233
3.9 Team Member Performance Assessment: Systems Assurance235
3.10 Issue Log: Systems Assurance237
4.0 Monitoring and Controlling Process Group: Systems Assurance239
4.1 Project Performance Report: Systems Assurance241
4.2 Variance Analysis: Systems Assurance243
4.3 Earned Value Status: Systems Assurance245
4.4 Risk Audit: Systems Assurance247
4.5 Contractor Status Report: Systems Assurance249
4.6 Formal Acceptance: Systems Assurance251
5.0 Closing Process Group: Systems Assurance253
5.1 Procurement Audit: Systems Assurance255
5.2 Contract Close-Out: Systems Assurance257
5.3 Project or Phase Close-Out: Systems Assurance259
5.4 Lessons Learned: Systems Assurance261
Index263
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. Will Systems assurance deliverables need to be tested and, if so, by whom?
<--- Score
2. Does the problem have ethical dimensions?
<--- Score
3. What Systems assurance events should you attend?
<--- Score
4. Is it needed?
<--- Score
5. What are the timeframes required to resolve each of the issues/problems?
<--- Score
6. What needs to be done?
<--- Score
7. Do you recognize Systems assurance achievements?
<--- Score
8. Are controls defined to recognize and contain problems?
<--- Score
9. What Systems assurance problem should be solved?
<--- Score
10. What are your needs in relation to Systems assurance skills, labor, equipment, and markets?
<--- Score
11. What is the recognized need?
<--- Score
12. What problems are you facing and how do you consider Systems assurance will circumvent those obstacles?
<--- Score
13. What situation(s) led to this Systems assurance Self Assessment?
<--- Score
14. What does Systems assurance success mean to the stakeholders?
<--- Score
15. What else needs to be measured?
<--- Score
16. Do you need to avoid or amend any Systems assurance activities?
<--- Score
17. Who are your key stakeholders who need to sign off?
<--- Score
18. What do employees need in the short term?
<--- Score
19. What is the smallest subset of the problem you can usefully solve?
<--- Score
20. What prevents you from making the changes you know will make you a more effective Systems assurance leader?
<--- Score
21. To what extent would your organization benefit from being recognized as a award recipient?
<--- Score
22. What Systems assurance coordination do you need?
<--- Score
23. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
24. What extra resources will you need?
<--- Score
25. What activities does the governance board need to consider?
<--- Score
26. Are employees recognized for desired behaviors?
<--- Score
27. What is the Systems assurance problem definition? What do you need to resolve?
<--- Score
28. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
29. What are the clients issues and concerns?
<--- Score
30. Who should resolve the Systems assurance issues?
СКАЧАТЬ