<--- Score
97. What information should you gather?
<--- Score
98. What Open System Environment services do you require?
<--- Score
99. Has/have the customer(s) been identified?
<--- Score
100. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
101. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
102. How did the Open System Environment manager receive input to the development of a Open System Environment improvement plan and the estimated completion dates/times of each activity?
<--- Score
103. Has your scope been defined?
<--- Score
104. What intelligence can you gather?
<--- Score
105. Have all of the relationships been defined properly?
<--- Score
106. How do you gather Open System Environment requirements?
<--- Score
107. How can the value of Open System Environment be defined?
<--- Score
108. Is there a critical path to deliver Open System Environment results?
<--- Score
109. Do you all define Open System Environment in the same way?
<--- Score
110. What customer feedback methods were used to solicit their input?
<--- Score
111. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
112. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
113. What is a worst-case scenario for losses?
<--- Score
114. What is the scope of the Open System Environment effort?
<--- Score
115. How do you manage changes in Open System Environment requirements?
<--- Score
116. What defines best in class?
<--- Score
117. Where can you gather more information?
<--- Score
118. Is the Open System Environment scope manageable?
<--- Score
119. What is the worst case scenario?
<--- Score
120. How do you think the partners involved in Open System Environment would have defined success?
<--- Score
121. How do you gather the stories?
<--- Score
122. Are roles and responsibilities formally defined?
<--- Score
123. Are the Open System Environment requirements complete?
<--- Score
124. Is the scope of Open System Environment defined?
<--- Score
125. Is special Open System Environment user knowledge required?
<--- Score
126. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
127. What is out of scope?
<--- Score
128. When is/was the Open System Environment start date?
<--- Score
129. How do you build the right business case?
<--- Score
130. What are (control) requirements for Open System Environment Information?
<--- Score
131. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
132. What gets examined?
<--- Score
133. 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
134. Are resources adequate for the scope?
<--- Score
135. 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
136. Is there a clear Open System Environment case definition?
<--- Score
137. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
138. What key stakeholder process output measure(s) does Open System Environment leverage and how?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer
