Has a team charter been developed and communicated?
<--- Score
60. What are the compelling stakeholder reasons for embarking on System in a package?
<--- Score
61. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
62. Is System in a package currently on schedule according to the plan?
<--- Score
63. How do you think the partners involved in System in a package would have defined success?
<--- Score
64. How would you define the culture at your organization, how susceptible is it to System in a package changes?
<--- Score
65. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
66. Do you have organizational privacy requirements?
<--- Score
67. Is the System in a package scope complete and appropriately sized?
<--- Score
68. What is out of scope?
<--- Score
69. Are there different segments of customers?
<--- Score
70. Are all requirements met?
<--- Score
71. How have you defined all System in a package requirements first?
<--- Score
72. Are there any constraints known that bear on the ability to perform System in a package work? How is the team addressing them?
<--- Score
73. What key stakeholder process output measure(s) does System in a package leverage and how?
<--- Score
74. Is System in a package required?
<--- Score
75. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
76. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
77. What are the tasks and definitions?
<--- Score
78. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
79. When is/was the System in a package start date?
<--- Score
80. What are the core elements of the System in a package business case?
<--- Score
81. What is the scope of the System in a package work?
<--- Score
82. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
83. Are resources adequate for the scope?
<--- Score
84. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
85. What information do you gather?
<--- Score
86. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
87. 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
88. Is the scope of System in a package defined?
<--- Score
89. How did the System in a package manager receive input to the development of a System in a package improvement plan and the estimated completion dates/times of each activity?
<--- Score
90. Who defines (or who defined) the rules and roles?
<--- Score
91. How will variation in the actual durations of each activity be dealt with to ensure that the expected System in a package results are met?
<--- Score
92. What are the System in a package tasks and definitions?
<--- Score
93. Is there a critical path to deliver System in a package results?
<--- Score
94. If substitutes have been appointed, have they been briefed on the System in a package goals and received regular communications as to the progress to date?
<--- Score
95. Has the direction changed at all during the course of System in a package? If so, when did it change and why?
<--- Score
96. What is the scope of System in a package?
<--- Score
97. How do you build the right business case?
<--- Score
98. What System in a package services do you require?
<--- Score
99. Have all of the relationships been defined properly?
<--- Score
100. What is the worst case scenario?
<--- Score
101.
