efforts?
<--- Score
100. Are all requirements met?
<--- Score
101. What constraints exist that might impact the team?
<--- Score
102. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
103. What are the dynamics of the communication plan?
<--- Score
104. 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
105. Is System Design Review linked to key stakeholder goals and objectives?
<--- Score
106. Is System Design Review currently on schedule according to the plan?
<--- Score
107. What scope do you want your strategy to cover?
<--- Score
108. Is there a System Design Review management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
109. Is there a critical path to deliver System Design Review results?
<--- Score
110. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
111. What would be the goal or target for a System Design Review’s improvement team?
<--- Score
112. How is the team tracking and documenting its work?
<--- Score
113. What happens if System Design Review’s scope changes?
<--- Score
114. Are task requirements clearly defined?
<--- Score
115. What system do you use for gathering System Design Review information?
<--- Score
116. Are the System Design Review requirements testable?
<--- Score
117. How do you manage scope?
<--- Score
118. Who is gathering System Design Review information?
<--- Score
119. Are resources adequate for the scope?
<--- Score
120. How do you gather System Design Review requirements?
<--- Score
121. Is the work to date meeting requirements?
<--- Score
122. How do you build the right business case?
<--- Score
123. How have you defined all System Design Review requirements first?
<--- Score
124. What is the context?
<--- Score
125. What gets examined?
<--- Score
126. What critical content must be communicated – who, what, when, where, and how?
<--- Score
127. What are the requirements for audit information?
<--- Score
128. What sort of initial information to gather?
<--- Score
129. What are the record-keeping requirements of System Design Review activities?
<--- Score
130. What are the System Design Review tasks and definitions?
<--- Score
131. Have all of the relationships been defined properly?
<--- Score
132. What are the rough order estimates on cost savings/opportunities that System Design Review brings?
<--- Score
133. How will the System Design Review team and the group measure complete success of System Design Review?
<--- Score
134. How did the System Design Review manager receive input to the development of a System Design Review improvement plan and the estimated completion dates/times of each activity?
<--- Score
135. What is a worst-case scenario for losses?
<--- Score
136. Why are you doing System Design Review and what is the scope?
<--- Score
137. Is the team sponsored by a champion or stakeholder leader?
<--- Score
138. How do you manage changes in System Design Review requirements?
<--- Score
139. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
140. What was the context?
<--- Score
141. Is System Design Review required?
<--- Score
142. How would you define the culture at your organization, how susceptible is it to System Design Review changes?
<--- Score
Add up total points for this section: _____ = Total points for this section
