style="font-size:15px;"> <--- Score
104. Are stakeholder processes mapped?
<--- Score
105. What is the scope of the DRIVE Technology work?
<--- Score
106. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
107. Is it clearly defined in and to your organization what you do?
<--- Score
108. How would you define the culture at your organization, how susceptible is it to DRIVE Technology changes?
<--- Score
109. What are the dynamics of the communication plan?
<--- Score
110. What DRIVE Technology services do you require?
<--- Score
111. How do you manage unclear DRIVE Technology requirements?
<--- Score
112. Do you have a DRIVE Technology success story or case study ready to tell and share?
<--- Score
113. Is the DRIVE Technology scope manageable?
<--- Score
114. Is DRIVE Technology linked to key stakeholder goals and objectives?
<--- Score
115. Is the DRIVE Technology scope complete and appropriately sized?
<--- Score
116. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
117. Are roles and responsibilities formally defined?
<--- Score
118. Is the work to date meeting requirements?
<--- Score
119. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
120. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
121. What is the scope of the DRIVE Technology effort?
<--- Score
122. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
123. What is in the scope and what is not in scope?
<--- Score
124. 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
125. Is DRIVE Technology required?
<--- Score
126. What information should you gather?
<--- Score
127. Why are you doing DRIVE Technology and what is the scope?
<--- Score
128. Is scope creep really all bad news?
<--- Score
129. How do you gather requirements?
<--- Score
130. How would you define DRIVE Technology leadership?
<--- Score
131. What are the compelling stakeholder reasons for embarking on DRIVE Technology?
<--- Score
132. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
133. Has your scope been defined?
<--- Score
134. Have all basic functions of DRIVE Technology been defined?
<--- Score
135. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
136. Who defines (or who defined) the rules and roles?
<--- Score
137. How will variation in the actual durations of each activity be dealt with to ensure that the expected DRIVE Technology results are met?
<--- Score
138. Will team members perform DRIVE Technology work when assigned and in a timely fashion?
<--- Score
139. Has/have the customer(s) been identified?
<--- Score
140. Who approved the DRIVE Technology scope?
<--- Score
141. How do you hand over DRIVE Technology context?
<--- 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 your score to the DRIVE Technology Index at the beginning of the Self-Assessment.
CRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance and evolution of the situation.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
