103. What scope to assess?
<--- Score
104. What is in the scope and what is not in scope?
<--- Score
105. Is System Protection currently on schedule according to the plan?
<--- Score
106. How do you build the right business case?
<--- Score
107. Is the team equipped with available and reliable resources?
<--- Score
108. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
109. Who is gathering System Protection information?
<--- Score
110. Is there a System Protection management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
111. How do you manage unclear System Protection requirements?
<--- Score
112. How are consistent System Protection definitions important?
<--- Score
113. Are the System Protection requirements testable?
<--- Score
114. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
115. What are (control) requirements for System Protection Information?
<--- Score
116. What are the requirements for audit information?
<--- Score
117. How do you gather requirements?
<--- Score
118. What is a worst-case scenario for losses?
<--- Score
119. Are the System Protection requirements complete?
<--- Score
120. What gets examined?
<--- Score
121. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
122. What would be the goal or target for a System Protection’s improvement team?
<--- Score
123. Has the System Protection 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
124. How did the System Protection manager receive input to the development of a System Protection improvement plan and the estimated completion dates/times of each activity?
<--- Score
125. Is there any additional System Protection definition of success?
<--- Score
126. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
127. Why are you doing System Protection and what is the scope?
<--- Score
128. When is/was the System Protection start date?
<--- Score
129. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
130. Is special System Protection user knowledge required?
<--- Score
131. Has a System Protection requirement not been met?
<--- Score
132. What are the compelling stakeholder reasons for embarking on System Protection?
<--- Score
133. What is out of scope?
<--- Score
134. What are the record-keeping requirements of System Protection activities?
<--- Score
135. Are all requirements met?
<--- Score
136. What constraints exist that might impact the team?
<--- Score
137. How do you gather the stories?
<--- Score
138. What are the System Protection tasks and definitions?
<--- Score
139. 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 System Protection 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. What could cause you to change course?
<--- Score
