2.36 Procurement Management Plan: Software As A Secure Service212
2.37 Source Selection Criteria: Software As A Secure Service214
2.38 Stakeholder Management Plan: Software As A Secure Service216
2.39 Change Management Plan: Software As A Secure Service218
3.0 Executing Process Group: Software As A Secure Service220
3.1 Team Member Status Report: Software As A Secure Service222
3.2 Change Request: Software As A Secure Service224
3.3 Change Log: Software As A Secure Service226
3.4 Decision Log: Software As A Secure Service228
3.5 Quality Audit: Software As A Secure Service230
3.6 Team Directory: Software As A Secure Service233
3.7 Team Operating Agreement: Software As A Secure Service235
3.8 Team Performance Assessment: Software As A Secure Service237
3.9 Team Member Performance Assessment: Software As A Secure Service239
3.10 Issue Log: Software As A Secure Service241
4.0 Monitoring and Controlling Process Group: Software As A Secure Service243
4.1 Project Performance Report: Software As A Secure Service245
4.2 Variance Analysis: Software As A Secure Service247
4.3 Earned Value Status: Software As A Secure Service249
4.4 Risk Audit: Software As A Secure Service251
4.5 Contractor Status Report: Software As A Secure Service253
4.6 Formal Acceptance: Software As A Secure Service255
5.0 Closing Process Group: Software As A Secure Service257
5.1 Procurement Audit: Software As A Secure Service259
5.2 Contract Close-Out: Software As A Secure Service261
5.3 Project or Phase Close-Out: Software As A Secure Service263
5.4 Lessons Learned: Software As A Secure Service265
Index267
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. What needs to stay?
<--- Score
2. Are controls defined to recognize and contain problems?
<--- Score
3. Which issues are too important to ignore?
<--- Score
4. Who defines the rules in relation to any given issue?
<--- Score
5. Which needs are not included or involved?
<--- Score
6. What is the smallest subset of the problem you can usefully solve?
<--- Score
7. What creative shifts do you need to take?
<--- Score
8. Does the problem have ethical dimensions?
<--- Score
9. Do you need to avoid or amend any Software as a secure service activities?
<--- Score
10. Who else hopes to benefit from it?
<--- Score
11. To what extent does each concerned units management team recognize Software as a secure service as an effective investment?
<--- Score
12. What situation(s) led to this Software as a secure service Self Assessment?
<--- Score
13. Are there recognized Software as a secure service problems?
<--- Score
14. How do you identify subcontractor relationships?
<--- Score
15. Is the need for organizational change recognized?
<--- Score
16. What is the Software as a secure service problem definition? What do you need to resolve?
<--- Score
17. How does it fit into your organizational needs and tasks?
<--- Score
18. What Software as a secure service problem should be solved?
<--- Score
19. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
20. Are there any revenue recognition issues?
<--- Score
21. What do you need to start doing?
<--- Score
22. 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
23. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
24. Who are your key stakeholders who need to sign off?
<--- Score
25. What do employees need in the short term?
<--- Score
26.
