What sort of initial information to gather?
<--- Score
93. Are resources adequate for the scope?
<--- Score
94. Does the team have regular meetings?
<--- Score
95. How do you manage changes in Open source appropriate technology requirements?
<--- Score
96. Is the Open source appropriate technology scope manageable?
<--- Score
97. What are the Open source appropriate technology tasks and definitions?
<--- Score
98. What is out of scope?
<--- Score
99. How will the Open source appropriate technology team and the group measure complete success of Open source appropriate technology?
<--- Score
100. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
101. How do you catch Open source appropriate technology definition inconsistencies?
<--- Score
102. Are task requirements clearly defined?
<--- Score
103. Who is gathering information?
<--- Score
104. How are consistent Open source appropriate technology definitions important?
<--- Score
105. How and when will the baselines be defined?
<--- Score
106. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
107. What customer feedback methods were used to solicit their input?
<--- Score
108. Are approval levels defined for contracts and supplements to contracts?
<--- Score
109. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
110. Where can you gather more information?
<--- Score
111. What are the core elements of the Open source appropriate technology business case?
<--- Score
112. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
113. What system do you use for gathering Open source appropriate technology information?
<--- Score
114. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
115. Is Open source appropriate technology linked to key stakeholder goals and objectives?
<--- Score
116. What baselines are required to be defined and managed?
<--- Score
117. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
118. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
119. Who is gathering Open source appropriate technology information?
<--- Score
120. What gets examined?
<--- Score
121. Have all basic functions of Open source appropriate technology been defined?
<--- Score
122. When is the estimated completion date?
<--- Score
123. Who approved the Open source appropriate technology scope?
<--- Score
124. What defines best in class?
<--- Score
125. 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
126. What is the definition of success?
<--- Score
127. Will a Open source appropriate technology production readiness review be required?
<--- Score
128. How did the Open source appropriate technology manager receive input to the development of a Open source appropriate technology improvement plan and the estimated completion dates/times of each activity?
<--- Score
129. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
130. How do you hand over Open source appropriate technology context?
<--- Score
131. What information should you gather?
<--- Score
132. Have specific policy objectives been defined?
<--- Score
133. What is the definition of Open source appropriate technology excellence?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of
