Risk Data Sheet: Information Systems Discipline208
2.36 Procurement Management Plan: Information Systems Discipline210
2.37 Source Selection Criteria: Information Systems Discipline212
2.38 Stakeholder Management Plan: Information Systems Discipline214
2.39 Change Management Plan: Information Systems Discipline216
3.0 Executing Process Group: Information Systems Discipline218
3.1 Team Member Status Report: Information Systems Discipline220
3.2 Change Request: Information Systems Discipline222
3.3 Change Log: Information Systems Discipline224
3.4 Decision Log: Information Systems Discipline226
3.5 Quality Audit: Information Systems Discipline228
3.6 Team Directory: Information Systems Discipline231
3.7 Team Operating Agreement: Information Systems Discipline233
3.8 Team Performance Assessment: Information Systems Discipline235
3.9 Team Member Performance Assessment: Information Systems Discipline238
3.10 Issue Log: Information Systems Discipline240
4.0 Monitoring and Controlling Process Group: Information Systems Discipline242
4.1 Project Performance Report: Information Systems Discipline244
4.2 Variance Analysis: Information Systems Discipline246
4.3 Earned Value Status: Information Systems Discipline248
4.4 Risk Audit: Information Systems Discipline250
4.5 Contractor Status Report: Information Systems Discipline252
4.6 Formal Acceptance: Information Systems Discipline254
5.0 Closing Process Group: Information Systems Discipline256
5.1 Procurement Audit: Information Systems Discipline258
5.2 Contract Close-Out: Information Systems Discipline260
5.3 Project or Phase Close-Out: Information Systems Discipline262
5.4 Lessons Learned: Information Systems Discipline264
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. Are there regulatory / compliance issues?
<--- Score
2. Does your organization need more Information systems discipline education?
<--- Score
3. What are the expected benefits of Information systems discipline to the stakeholder?
<--- Score
4. What do employees need in the short term?
<--- Score
5. What extra resources will you need?
<--- Score
6. What is the Information systems discipline problem definition? What do you need to resolve?
<--- Score
7. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
8. What is the extent or complexity of the Information systems discipline problem?
<--- Score
9. What should be considered when identifying available resources, constraints, and deadlines?
<--- Score
10. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
11. What Information systems discipline coordination do you need?
<--- Score
12. Does Information systems discipline create potential expectations in other areas that need to be recognized and considered?
<--- Score
13. Where do you need to exercise leadership?
<--- Score
14. What needs to stay?
<--- Score
15. Are controls defined to recognize and contain problems?
<--- Score
16. Will it solve real problems?
<--- Score
17. How do you identify the kinds of information that you will need?
<--- Score
18. How do you recognize an objection?
<--- Score
19. Is the quality assurance team identified?
<--- Score
20. How do you identify subcontractor relationships?
<--- Score
21. How do you recognize an Information systems discipline objection?
<--- Score
22. What are your needs in relation to Information systems discipline skills, labor, equipment, and markets?
<--- Score
23. How do you take a forward-looking perspective in identifying Information systems discipline research related to market response and models?
<--- Score
24. What are the minority interests and what amount of minority interests can
