who, what, when, where, and how?
<--- Score
104. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
105. How do you manage unclear Systems assurance requirements?
<--- Score
106. Are accountability and ownership for Systems assurance clearly defined?
<--- Score
107. Are all requirements met?
<--- Score
108. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
109. What is the worst case scenario?
<--- Score
110. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
111. Do you have organizational privacy requirements?
<--- Score
112. How have you defined all Systems assurance requirements first?
<--- Score
113. Is there any additional Systems assurance definition of success?
<--- Score
114. Is the work to date meeting requirements?
<--- Score
115. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
116. What Systems assurance requirements should be gathered?
<--- Score
117. Has a Systems assurance requirement not been met?
<--- Score
118. What is a worst-case scenario for losses?
<--- Score
119. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
120. What would be the goal or target for a Systems assurance’s improvement team?
<--- Score
121. What is the definition of success?
<--- Score
122. What are the compelling stakeholder reasons for embarking on Systems assurance?
<--- Score
123. 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
124. What is the context?
<--- Score
125. What defines best in class?
<--- Score
126. Has your scope been defined?
<--- Score
127. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
128. Are roles and responsibilities formally defined?
<--- Score
129. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
130. What customer feedback methods were used to solicit their input?
<--- Score
131. Is Systems assurance currently on schedule according to the plan?
<--- Score
132. Are approval levels defined for contracts and supplements to contracts?
<--- Score
133. What sort of initial information to gather?
<--- Score
134. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
135. What is out of scope?
<--- Score
136. Scope of sensitive information?
<--- Score
137. What is the scope of the Systems assurance effort?
<--- Score
138. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
139. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
140. What is the scope of the Systems assurance work?
<--- Score
141. What are the rough order estimates on cost savings/opportunities that Systems assurance brings?
<--- 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 Systems assurance 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
