Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
5. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
6. Is Project management application required?
<--- Score
7. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
8. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
9. How is the team tracking and documenting its work?
<--- Score
10. What is the scope of the Project management application effort?
<--- Score
11. Are accountability and ownership for Project management application clearly defined?
<--- Score
12. Is the scope of Project management application defined?
<--- Score
13. Is the team equipped with available and reliable resources?
<--- Score
14. Are there any constraints known that bear on the ability to perform Project management application work? How is the team addressing them?
<--- Score
15. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
16. How do you gather requirements?
<--- Score
17. Has the direction changed at all during the course of Project management application? If so, when did it change and why?
<--- Score
18. Is scope creep really all bad news?
<--- Score
19. Is Project management application linked to key stakeholder goals and objectives?
<--- Score
20. What is out-of-scope initially?
<--- Score
21. How do you catch Project management application definition inconsistencies?
<--- Score
22. What is the worst case scenario?
<--- Score
23. Is there a Project management application management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
24. Are all requirements met?
<--- Score
25. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
26. Has a Project management application requirement not been met?
<--- Score
27. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
28. Scope of sensitive information?
<--- Score
29. Has your scope been defined?
<--- Score
30. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
31. Who are the Project management application improvement team members, including Management Leads and Coaches?
<--- Score
32. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
33. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
34. What defines best in class?
<--- Score
35. What system do you use for gathering Project management application information?
<--- Score
36. Are the Project management application requirements testable?
<--- Score
37. How do you manage changes in Project management application requirements?
<--- Score
38. Is there a critical path to deliver Project management application results?
<--- Score
39. Is it clearly defined in and to your organization what you do?
<--- Score
40. What critical content must be communicated – who, what, when, where, and how?
<--- Score
41. What baselines are required to be defined and managed?
<--- Score
42. Is the Project management application scope manageable?
<--- Score
43. What are the Project management application tasks and definitions?
<--- Score
44. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
45. Are required metrics defined, what are they?
<--- Score
46. Who is gathering Project management application information?
<---
