3.6 Team Directory: ELK Stack225
3.7 Team Operating Agreement: ELK Stack227
3.8 Team Performance Assessment: ELK Stack229
3.9 Team Member Performance Assessment: ELK Stack231
3.10 Issue Log: ELK Stack233
4.0 Monitoring and Controlling Process Group: ELK Stack235
4.1 Project Performance Report: ELK Stack237
4.2 Variance Analysis: ELK Stack239
4.3 Earned Value Status: ELK Stack241
4.4 Risk Audit: ELK Stack243
4.5 Contractor Status Report: ELK Stack245
4.6 Formal Acceptance: ELK Stack247
5.0 Closing Process Group: ELK Stack249
5.1 Procurement Audit: ELK Stack251
5.2 Contract Close-Out: ELK Stack253
5.3 Project or Phase Close-Out: ELK Stack255
5.4 Lessons Learned: ELK Stack257
Index259
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. What extra resources will you need?
<--- Score
2. Who else hopes to benefit from it?
<--- Score
3. What ELK stack problem should be solved?
<--- Score
4. What ELK stack capabilities do you need?
<--- Score
5. How do you identify subcontractor relationships?
<--- Score
6. Are controls defined to recognize and contain problems?
<--- Score
7. What should be considered when identifying available resources, constraints, and deadlines?
<--- 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. Will ELK stack deliverables need to be tested and, if so, by whom?
<--- Score
10. What vendors make products that address the ELK stack needs?
<--- Score
11. Do you recognize ELK stack achievements?
<--- Score
12. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
13. How are you going to measure success?
<--- Score
14. Did you miss any major ELK stack issues?
<--- Score
15. For your ELK stack project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
16. Does the problem have ethical dimensions?
<--- Score
17. What ELK stack events should you attend?
<--- Score
18. Have you identified your ELK stack key performance indicators?
<--- Score
19. How do you identify the kinds of information that you will need?
<--- Score
20. Do you need to avoid or amend any ELK stack activities?
<--- Score
21. Which needs are not included or involved?
<--- Score
22. What is the extent or complexity of the ELK stack problem?
<--- Score
23. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
24. What is the recognized need?
<--- Score
25. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
26. Consider your own ELK stack project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
27. Will new equipment/products be required to facilitate ELK stack delivery, for example is new software needed?
<--- Score
28. Are employees recognized for desired behaviors?
<--- Score
29. Are problem definition and motivation clearly presented?
<--- Score
30. What would happen if ELK stack weren’t done?
<--- Score
31. What tools and technologies are needed for a custom ELK stack project?
<--- Score
32. What needs to stay?
<---
