Status Report: Protocol Systems215
3.2 Change Request: Protocol Systems217
3.3 Change Log: Protocol Systems219
3.4 Decision Log: Protocol Systems221
3.5 Quality Audit: Protocol Systems223
3.6 Team Directory: Protocol Systems226
3.7 Team Operating Agreement: Protocol Systems228
3.8 Team Performance Assessment: Protocol Systems230
3.9 Team Member Performance Assessment: Protocol Systems232
3.10 Issue Log: Protocol Systems234
4.0 Monitoring and Controlling Process Group: Protocol Systems236
4.1 Project Performance Report: Protocol Systems238
4.2 Variance Analysis: Protocol Systems240
4.3 Earned Value Status: Protocol Systems242
4.4 Risk Audit: Protocol Systems244
4.5 Contractor Status Report: Protocol Systems246
4.6 Formal Acceptance: Protocol Systems248
5.0 Closing Process Group: Protocol Systems250
5.1 Procurement Audit: Protocol Systems252
5.2 Contract Close-Out: Protocol Systems254
5.3 Project or Phase Close-Out: Protocol Systems256
5.4 Lessons Learned: Protocol Systems258
Index260
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 are the Protocol Systems’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
2. What is the problem and/or vulnerability?
<--- Score
3. What would happen if Protocol Systems weren’t done?
<--- Score
4. What vendors make products that address the Protocol Systems needs?
<--- Score
5. Who needs budgets?
<--- Score
6. What else needs to be measured?
<--- Score
7. Why the need?
<--- Score
8. Will new equipment/products be required to facilitate Protocol Systems delivery, for example is new software needed?
<--- Score
9. How many trainings, in total, are needed?
<--- Score
10. How are you going to measure success?
<--- Score
11. Can management personnel recognize the monetary benefit of Protocol Systems?
<--- Score
12. What tools and technologies are needed for a custom Protocol Systems project?
<--- Score
13. What are the Protocol Systems resources needed?
<--- Score
14. Where do you need to exercise leadership?
<--- Score
15. What activities does the governance board need to consider?
<--- Score
16. Will it solve real problems?
<--- Score
17. How much are sponsors, customers, partners, stakeholders involved in Protocol Systems? In other words, what are the risks, if Protocol Systems does not deliver successfully?
<--- Score
18. Who are your key stakeholders who need to sign off?
<--- Score
19. What is the smallest subset of the problem you can usefully solve?
<--- Score
20. How are training requirements identified?
<--- Score
21. What creative shifts do you need to take?
<--- Score
22. What Protocol Systems events should you attend?
<--- Score
23. Which issues are too important to ignore?
<--- Score
24. Are there Protocol Systems problems defined?
<--- Score
25. Do you recognize Protocol Systems achievements?
<--- Score
26. Are there any specific expectations or concerns about the Protocol Systems team, Protocol Systems itself?
<--- Score
27. Do you need different information or graphics?
<--- Score
28. How do you assess your Protocol Systems workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
29. How do you recognize an Protocol Systems objection?
<--- Score
30. How do you identify subcontractor relationships?
<---
