100. Have all of the relationships been defined properly?
<--- Score
101. What critical content must be communicated – who, what, when, where, and how?
<--- Score
102. Are approval levels defined for contracts and supplements to contracts?
<--- Score
103. Is there a critical path to deliver Decision support software results?
<--- Score
104. What are the Decision support software tasks and definitions?
<--- Score
105. How do you manage changes in Decision support software requirements?
<--- Score
106. What is the scope of Decision support software?
<--- Score
107. What is the worst case scenario?
<--- Score
108. What is the scope of the Decision support software effort?
<--- Score
109. How would you define the culture at your organization, how susceptible is it to Decision support software changes?
<--- Score
110. How have you defined all Decision support software requirements first?
<--- Score
111. What was the context?
<--- Score
112. What would be the goal or target for a Decision support software’s improvement team?
<--- Score
113. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
114. What scope to assess?
<--- Score
115. Who approved the Decision support software scope?
<--- Score
116. What key stakeholder process output measure(s) does Decision support software leverage and how?
<--- Score
117. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
118. What information do you gather?
<--- Score
119. What happens if Decision support software’s scope changes?
<--- Score
120. What are the rough order estimates on cost savings/opportunities that Decision support software brings?
<--- Score
121. Are task requirements clearly defined?
<--- Score
122. When is/was the Decision support software start date?
<--- Score
123. How can the value of Decision support software be defined?
<--- Score
124. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
125. How is the team tracking and documenting its work?
<--- Score
126. What are the requirements for audit information?
<--- Score
127. Has the Decision support software work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?
<--- Score
128. Is Decision support software linked to key stakeholder goals and objectives?
<--- Score
129. 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
130. Has the direction changed at all during the course of Decision support software? If so, when did it change and why?
<--- Score
131. What is out of scope?
<--- Score
132. Are roles and responsibilities formally defined?
<--- Score
133. The political context: who holds power?
<--- Score
134. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
135. Is Decision support software currently on schedule according to the plan?
<--- Score
136. 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
137. How would you define Decision support software leadership?
<--- Score
138. What is the definition of success?
<--- Score
139. What are the dynamics of the communication plan?
<--- Score
140. Is there any additional Decision support software definition of success?
<--- Score
141. Has a team charter been developed and communicated?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for
