Score
3. Has your scope been defined?
<--- Score
4. Are resources adequate for the scope?
<--- Score
5. What are the requirements for audit information?
<--- Score
6. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
7. When is/was the Emergency communication systems start date?
<--- Score
8. What are the tasks and definitions?
<--- Score
9. Have all of the relationships been defined properly?
<--- Score
10. What are (control) requirements for Emergency communication systems Information?
<--- Score
11. Are all requirements met?
<--- Score
12. How will the Emergency communication systems team and the group measure complete success of Emergency communication systems?
<--- Score
13. How and when will the baselines be defined?
<--- Score
14. What critical content must be communicated – who, what, when, where, and how?
<--- Score
15. How do you gather requirements?
<--- Score
16. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
17. What is the scope of the Emergency communication systems work?
<--- Score
18. If substitutes have been appointed, have they been briefed on the Emergency communication systems goals and received regular communications as to the progress to date?
<--- Score
19. Are stakeholder processes mapped?
<--- Score
20. Who approved the Emergency communication systems scope?
<--- Score
21. Is it clearly defined in and to your organization what you do?
<--- Score
22. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
23. Is Emergency communication systems linked to key stakeholder goals and objectives?
<--- Score
24. How often are the team meetings?
<--- Score
25. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
26. What Emergency communication systems services do you require?
<--- Score
27. How have you defined all Emergency communication systems requirements first?
<--- Score
28. How do you keep key subject matter experts in the loop?
<--- Score
29. Are task requirements clearly defined?
<--- Score
30. Has a team charter been developed and communicated?
<--- Score
31. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
32. What are the Emergency communication systems tasks and definitions?
<--- Score
33. How do you catch Emergency communication systems definition inconsistencies?
<--- Score
34. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
35. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?
<--- Score
36. What defines best in class?
<--- Score
37. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
38. Who defines (or who defined) the rules and roles?
<--- Score
39. What is in the scope and what is not in scope?
<--- Score
40. How will variation in the actual durations of each activity be dealt with to ensure that the expected Emergency communication systems results are met?
<--- Score
41. What baselines are required to be defined and managed?
<--- Score
42. Has/have the customer(s) been identified?
<--- Score
43. How do you hand over Emergency communication systems context?
<--- Score
44. How would you define the culture at your organization, how susceptible is it to Emergency communication systems changes?
<--- Score
45. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
