<--- Score
92. Are task requirements clearly defined?
<--- Score
93. Has a team charter been developed and communicated?
<--- Score
94. Where can you gather more information?
<--- Score
95. How will variation in the actual durations of each activity be dealt with to ensure that the expected Information systems discipline results are met?
<--- Score
96. Have specific policy objectives been defined?
<--- Score
97. How are consistent Information systems discipline definitions important?
<--- Score
98. What are the compelling stakeholder reasons for embarking on Information systems discipline?
<--- Score
99. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
100. Will a Information systems discipline production readiness review be required?
<--- Score
101. Is the team equipped with available and reliable resources?
<--- Score
102. 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
103. How often are the team meetings?
<--- Score
104. Have all of the relationships been defined properly?
<--- Score
105. What is out-of-scope initially?
<--- Score
106. When is the estimated completion date?
<--- Score
107. Is Information systems discipline currently on schedule according to the plan?
<--- Score
108. Are there different segments of customers?
<--- Score
109. What is a worst-case scenario for losses?
<--- Score
110. How would you define the culture at your organization, how susceptible is it to Information systems discipline changes?
<--- Score
111. Is there a clear Information systems discipline case definition?
<--- Score
112. Do you have organizational privacy requirements?
<--- Score
113. What scope to assess?
<--- Score
114. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
115. How do you gather the stories?
<--- Score
116. Is the work to date meeting requirements?
<--- Score
117. Does the team have regular meetings?
<--- Score
118. Who approved the Information systems discipline scope?
<--- Score
119. What is out of scope?
<--- Score
120. What are the dynamics of the communication plan?
<--- Score
121. What happens if Information systems discipline’s scope changes?
<--- Score
122. 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
123. Has your scope been defined?
<--- Score
124. What is the worst case scenario?
<--- Score
125. Has/have the customer(s) been identified?
<--- Score
126. Is Information systems discipline required?
<--- Score
127. How do you hand over Information systems discipline context?
<--- Score
128. What are the Information systems discipline tasks and definitions?
<--- Score
129. Is scope creep really all bad news?
<--- Score
130. What system do you use for gathering Information systems discipline information?
<--- Score
131. How do you build the right business case?
<--- Score
132. How do you think the partners involved in Information systems discipline would have defined success?
<--- Score
133. Have the customer needs been translated into specific, measurable requirements? 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 your score to the Information systems discipline Index at the beginning of the Self-Assessment.
CRITERION
