Score
7. What intelligence can you gather?
<--- Score
8. Do you all define Automated Pain Recognition in the same way?
<--- Score
9. What sort of initial information to gather?
<--- Score
10. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
11. Do you have a Automated Pain Recognition success story or case study ready to tell and share?
<--- Score
12. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
13. Is special Automated Pain Recognition user knowledge required?
<--- Score
14. What is the definition of success?
<--- Score
15. Are the Automated Pain Recognition requirements complete?
<--- Score
16. Are improvement team members fully trained on Automated Pain Recognition?
<--- Score
17. How would you define the culture at your organization, how susceptible is it to Automated Pain Recognition changes?
<--- Score
18. Have all of the relationships been defined properly?
<--- Score
19. Who are the Automated Pain Recognition improvement team members, including Management Leads and Coaches?
<--- Score
20. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
21. How will variation in the actual durations of each activity be dealt with to ensure that the expected Automated Pain Recognition results are met?
<--- Score
22. How do you catch Automated Pain Recognition definition inconsistencies?
<--- Score
23. What is the scope of the Automated Pain Recognition effort?
<--- Score
24. What sources do you use to gather information for a Automated Pain Recognition study?
<--- Score
25. What Automated Pain Recognition requirements should be gathered?
<--- Score
26. Are all requirements met?
<--- Score
27. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
28. Who defines (or who defined) the rules and roles?
<--- Score
29. Who is gathering Automated Pain Recognition information?
<--- Score
30. Is there a critical path to deliver Automated Pain Recognition results?
<--- Score
31. What are the dynamics of the communication plan?
<--- Score
32. Does the team have regular meetings?
<--- Score
33. How and when will the baselines be defined?
<--- Score
34. Where can you gather more information?
<--- Score
35. What is the context?
<--- Score
36. What customer feedback methods were used to solicit their input?
<--- Score
37. What constraints exist that might impact the team?
<--- Score
38. Will team members perform Automated Pain Recognition work when assigned and in a timely fashion?
<--- Score
39. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
40. What is the scope?
<--- Score
41. Is the scope of Automated Pain Recognition defined?
<--- Score
42. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
43. What key stakeholder process output measure(s) does Automated Pain Recognition leverage and how?
<--- Score
44. Is Automated Pain Recognition linked to key stakeholder goals and objectives?
<--- Score
45. When is the estimated completion date?
<--- Score
46. How does the Automated Pain Recognition manager ensure against scope creep?
<--- Score
47. What knowledge or experience is required?
<--- Score
48. How is the team tracking and documenting its work?
<--- Score
49. Is there a clear Automated Pain Recognition case definition?
<--- Score
50. Are resources adequate for the scope?
<---
