Score
15. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
16. Do you have a System in a package success story or case study ready to tell and share?
<--- Score
17. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
18. What customer feedback methods were used to solicit their input?
<--- Score
19. How do you manage scope?
<--- Score
20. Why are you doing System in a package and what is the scope?
<--- Score
21. How often are the team meetings?
<--- Score
22. How would you define System in a package leadership?
<--- Score
23. What sources do you use to gather information for a System in a package study?
<--- Score
24. Is there any additional System in a package definition of success?
<--- Score
25. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
26. What scope do you want your strategy to cover?
<--- Score
27. What is a worst-case scenario for losses?
<--- Score
28. Are the System in a package requirements testable?
<--- Score
29. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
30. 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?
<--- Score
31. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
32. What are the record-keeping requirements of System in a package activities?
<--- Score
33. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
34. What is the context?
<--- Score
35. Where can you gather more information?
<--- Score
36. Have specific policy objectives been defined?
<--- Score
37. What System in a package requirements should be gathered?
<--- Score
38. How is the team tracking and documenting its work?
<--- Score
39. What are the rough order estimates on cost savings/opportunities that System in a package brings?
<--- Score
40. Will team members perform System in a package work when assigned and in a timely fashion?
<--- Score
41. What is in the scope and what is not in scope?
<--- Score
42. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
43. The political context: who holds power?
<--- Score
44. How do you catch System in a package definition inconsistencies?
<--- Score
45. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
46. What gets examined?
<--- Score
47. 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
48. What knowledge or experience is required?
<--- Score
49. Are audit criteria, scope, frequency and methods defined?
<--- Score
50. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
51. What would be the goal or target for a System in a package’s improvement team?
<--- Score
52. How can the value of System in a package be defined?
<--- Score
53. How and when will the baselines be defined?
<--- Score
54. What is in scope?
<--- Score
55. What are the requirements for audit information?
<--- Score
56. How do you gather requirements?
<--- Score
57. What is the definition of success?
<--- Score
58. Is there a clear System in a package case definition?
<--- Score
