Change Management Plan: Firmware As A Service213
3.0 Executing Process Group: Firmware As A Service215
3.1 Team Member Status Report: Firmware As A Service217
3.2 Change Request: Firmware As A Service219
3.3 Change Log: Firmware As A Service221
3.4 Decision Log: Firmware As A Service223
3.5 Quality Audit: Firmware As A Service225
3.6 Team Directory: Firmware As A Service228
3.7 Team Operating Agreement: Firmware As A Service230
3.8 Team Performance Assessment: Firmware As A Service232
3.9 Team Member Performance Assessment: Firmware As A Service234
3.10 Issue Log: Firmware As A Service236
4.0 Monitoring and Controlling Process Group: Firmware As A Service238
4.1 Project Performance Report: Firmware As A Service240
4.2 Variance Analysis: Firmware As A Service242
4.3 Earned Value Status: Firmware As A Service244
4.4 Risk Audit: Firmware As A Service246
4.5 Contractor Status Report: Firmware As A Service248
4.6 Formal Acceptance: Firmware As A Service250
5.0 Closing Process Group: Firmware As A Service252
5.1 Procurement Audit: Firmware As A Service254
5.2 Contract Close-Out: Firmware As A Service256
5.3 Project or Phase Close-Out: Firmware As A Service258
5.4 Lessons Learned: Firmware As A Service260
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. Will it solve real problems?
<--- Score
2. 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
3. How do you recognize an Firmware as a Service objection?
<--- Score
4. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
5. Which needs are not included or involved?
<--- Score
6. How are training requirements identified?
<--- Score
7. Are there recognized Firmware as a Service problems?
<--- Score
8. Where is training needed?
<--- Score
9. How do you identify the kinds of information that you will need?
<--- Score
10. Are there any specific expectations or concerns about the Firmware as a Service team, Firmware as a Service itself?
<--- Score
11. Who are your key stakeholders who need to sign off?
<--- Score
12. What information do users need?
<--- Score
13. How much are sponsors, customers, partners, stakeholders involved in Firmware as a Service? In other words, what are the risks, if Firmware as a Service does not deliver successfully?
<--- Score
14. Who should resolve the Firmware as a Service issues?
<--- Score
15. Who needs what information?
<--- Score
16. Does your organization need more Firmware as a Service education?
<--- Score
17. What are the stakeholder objectives to be achieved with Firmware as a Service?
<--- Score
18. For your Firmware as a Service project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
19. Are employees recognized for desired behaviors?
<--- Score
20. What is the smallest subset of the problem you can usefully solve?
<--- Score
21. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
22. How many trainings, in total, are needed?
<--- Score
23. How do you assess your Firmware as a Service workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
24. Which issues are too important to ignore?
<--- Score
25. What Firmware as a Service capabilities do you need?
<--- Score
26. What are the Firmware as a Service resources needed?
<--- Score
27. Do you know what you need to know about Firmware as a Service?
