When is the estimated completion date?
<--- Score
102. How do you manage unclear System in a package requirements?
<--- Score
103. Will a System in a package production readiness review be required?
<--- Score
104. Will team members regularly document their System in a package work?
<--- Score
105. What baselines are required to be defined and managed?
<--- Score
106. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
107. Is the team equipped with available and reliable resources?
<--- Score
108. What defines best in class?
<--- Score
109. Is it clearly defined in and to your organization what you do?
<--- Score
110. How does the System in a package manager ensure against scope creep?
<--- Score
111. What scope to assess?
<--- Score
112. How do you gather the stories?
<--- Score
113. Who approved the System in a package scope?
<--- Score
114. What is out-of-scope initially?
<--- Score
115. Is there a System in a package management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
116. Are approval levels defined for contracts and supplements to contracts?
<--- Score
117. What intelligence can you gather?
<--- Score
118. What is the definition of System in a package excellence?
<--- Score
119. Are roles and responsibilities formally defined?
<--- Score
120. Is System in a package linked to key stakeholder goals and objectives?
<--- Score
121. What happens if System in a package’s scope changes?
<--- Score
122. What constraints exist that might impact the team?
<--- Score
123. What system do you use for gathering System in a package information?
<--- Score
124. Does the team have regular meetings?
<--- Score
125. How will the System in a package team and the group measure complete success of System in a package?
<--- Score
126. Are the System in a package requirements complete?
<--- Score
127. How do you hand over System in a package context?
<--- Score
128. Has/have the customer(s) been identified?
<--- Score
129. Has a System in a package requirement not been met?
<--- Score
130. What information should you gather?
<--- Score
131. Is special System in a package user knowledge required?
<--- Score
132. Who is gathering System in a package information?
<--- Score
133. Are task requirements clearly defined?
<--- Score
134. Have all basic functions of System in a package been defined?
<--- Score
135. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
136. Who are the System in a package improvement team members, including Management Leads and Coaches?
<--- Score
137. Does the scope remain the same?
<--- Score
138. How do you gather System in a package requirements?
<--- 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 System in a package 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
1. How frequently do you track System in a package measures?
<--- Score
2. What are your operating costs?
<--- Score
