Software207
2.37 Source Selection Criteria: Vendor Management Software209
2.38 Stakeholder Management Plan: Vendor Management Software211
2.39 Change Management Plan: Vendor Management Software213
3.0 Executing Process Group: Vendor Management Software215
3.1 Team Member Status Report: Vendor Management Software217
3.2 Change Request: Vendor Management Software219
3.3 Change Log: Vendor Management Software221
3.4 Decision Log: Vendor Management Software223
3.5 Quality Audit: Vendor Management Software225
3.6 Team Directory: Vendor Management Software228
3.7 Team Operating Agreement: Vendor Management Software230
3.8 Team Performance Assessment: Vendor Management Software232
3.9 Team Member Performance Assessment: Vendor Management Software234
3.10 Issue Log: Vendor Management Software236
4.0 Monitoring and Controlling Process Group: Vendor Management Software238
4.1 Project Performance Report: Vendor Management Software240
4.2 Variance Analysis: Vendor Management Software242
4.3 Earned Value Status: Vendor Management Software244
4.4 Risk Audit: Vendor Management Software246
4.5 Contractor Status Report: Vendor Management Software248
4.6 Formal Acceptance: Vendor Management Software250
5.0 Closing Process Group: Vendor Management Software252
5.1 Procurement Audit: Vendor Management Software254
5.2 Contract Close-Out: Vendor Management Software256
5.3 Project or Phase Close-Out: Vendor Management Software258
5.4 Lessons Learned: Vendor Management Software260
Index262
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. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
2. Are there recognized Vendor Management Software problems?
<--- Score
3. What creative shifts do you need to take?
<--- Score
4. When a Vendor Management Software manager recognizes a problem, what options are available?
<--- Score
5. What do you need to start doing?
<--- Score
6. Did you miss any major Vendor Management Software issues?
<--- Score
7. Are there any revenue recognition issues?
<--- Score
8. 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
9. Does Vendor Management Software create potential expectations in other areas that need to be recognized and considered?
<--- Score
10. Which needs are not included or involved?
<--- Score
11. What are the clients issues and concerns?
<--- Score
12. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
13. What are the Vendor Management Software resources needed?
<--- Score
14. Who needs budgets?
<--- Score
15. How do you identify subcontractor relationships?
<--- Score
16. Who needs to know?
<--- Score
17. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
18. What are the expected benefits of Vendor Management Software to the stakeholder?
<--- Score
19. What else needs to be measured?
<--- Score
20. Are there Vendor Management Software problems defined?
<--- Score
21. What is the extent or complexity of the Vendor Management Software problem?
<--- Score
22. Who are your key stakeholders who need to sign off?
<--- Score
23. How many trainings, in total, are needed?
<--- Score
24. Is it needed?
<--- Score
25. Are employees recognized for desired behaviors?
<--- Score
26. Do you need different information or graphics?
<--- Score
27.
