2.34 Probability and Impact Matrix: Contract Risk Management Software206
2.35 Risk Data Sheet: Contract Risk Management Software208
2.36 Procurement Management Plan: Contract Risk Management Software210
2.37 Source Selection Criteria: Contract Risk Management Software212
2.38 Stakeholder Management Plan: Contract Risk Management Software214
2.39 Change Management Plan: Contract Risk Management Software216
3.0 Executing Process Group: Contract Risk Management Software218
3.1 Team Member Status Report: Contract Risk Management Software220
3.2 Change Request: Contract Risk Management Software222
3.3 Change Log: Contract Risk Management Software224
3.4 Decision Log: Contract Risk Management Software226
3.5 Quality Audit: Contract Risk Management Software228
3.6 Team Directory: Contract Risk Management Software231
3.7 Team Operating Agreement: Contract Risk Management Software233
3.8 Team Performance Assessment: Contract Risk Management Software235
3.9 Team Member Performance Assessment: Contract Risk Management Software237
3.10 Issue Log: Contract Risk Management Software239
4.0 Monitoring and Controlling Process Group: Contract Risk Management Software241
4.1 Project Performance Report: Contract Risk Management Software243
4.2 Variance Analysis: Contract Risk Management Software245
4.3 Earned Value Status: Contract Risk Management Software247
4.4 Risk Audit: Contract Risk Management Software249
4.5 Contractor Status Report: Contract Risk Management Software251
4.6 Formal Acceptance: Contract Risk Management Software253
5.0 Closing Process Group: Contract Risk Management Software255
5.1 Procurement Audit: Contract Risk Management Software257
5.2 Contract Close-Out: Contract Risk Management Software260
5.3 Project or Phase Close-Out: Contract Risk Management Software262
5.4 Lessons Learned: Contract Risk Management Software264
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. How many trainings, in total, are needed?
<--- Score
2. What creative shifts do you need to take?
<--- Score
3. 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
4. What prevents you from making the changes you know will make you a more effective Contract risk management software leader?
<--- Score
5. Will Contract risk management software deliverables need to be tested and, if so, by whom?
<--- Score
6. What do you need to start doing?
<--- Score
7. How do you take a forward-looking perspective in identifying Contract risk management software research related to market response and models?
<--- Score
8. How do you recognize an objection?
<--- Score
9. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
10. What activities does the governance board need to consider?
<--- Score
11. Who defines the rules in relation to any given issue?
<--- Score
12. Can management personnel recognize the monetary benefit of Contract risk management software?
<--- Score
13. Do you need to avoid or amend any Contract risk management software activities?
<--- Score
14. What vendors make products that address the Contract risk management software needs?
<--- Score
15. What are the expected benefits of Contract risk management software to the stakeholder?
<--- Score
16. Is the quality assurance team identified?
<--- Score
17. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
18. What problems are you facing and how do you consider Contract risk management software will circumvent those obstacles?
<--- Score
19. Are controls defined to recognize and contain problems?
<--- Score
20. Are problem definition and motivation clearly presented?
<--- Score
21. What Contract risk management software capabilities do you need?
<--- Score
22. What Contract risk management software events should
