Score
104. Is the Information systems security engineering scope complete and appropriately sized?
<--- Score
105. Is there a clear Information systems security engineering case definition?
<--- Score
106. What are the record-keeping requirements of Information systems security engineering activities?
<--- Score
107. Does the team have regular meetings?
<--- Score
108. How do you think the partners involved in Information systems security engineering would have defined success?
<--- Score
109. What are the dynamics of the communication plan?
<--- Score
110. What is the worst case scenario?
<--- Score
111. 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
112. Is Information systems security engineering linked to key stakeholder goals and objectives?
<--- Score
113. Who are the Information systems security engineering improvement team members, including Management Leads and Coaches?
<--- Score
114. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
115. What are the tasks and definitions?
<--- Score
116. What constraints exist that might impact the team?
<--- Score
117. What sort of initial information to gather?
<--- Score
118. Are task requirements clearly defined?
<--- Score
119. What is the context?
<--- Score
120. What would be the goal or target for a Information systems security engineering’s improvement team?
<--- Score
121. If substitutes have been appointed, have they been briefed on the Information systems security engineering goals and received regular communications as to the progress to date?
<--- Score
122. What are the Information systems security engineering tasks and definitions?
<--- Score
123. How do you gather the stories?
<--- Score
124. The political context: who holds power?
<--- Score
125. Who defines (or who defined) the rules and roles?
<--- Score
126. Has your scope been defined?
<--- Score
127. How do you gather Information systems security engineering requirements?
<--- Score
128. Are roles and responsibilities formally defined?
<--- Score
129. Do you all define Information systems security engineering in the same way?
<--- Score
130. Has/have the customer(s) been identified?
<--- Score
131. What is a worst-case scenario for losses?
<--- Score
132. What is out of scope?
<--- Score
133. Will a Information systems security engineering production readiness review be required?
<--- Score
134. What information do you gather?
<--- 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 security engineering 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 will you measure your Information systems security engineering effectiveness?
<--- Score
2. Who should receive measurement reports?
<--- Score
3. Are supply costs steady or fluctuating?
<--- Score
4. How sensitive must the Information systems security engineering strategy be to cost?
<--- Score
5. How will you measure success?
<--- Score
6. What does losing customers cost your organization?
<--- Score
7. What does a Test Case verify?
<--- Score
8. Are missed Information systems security engineering opportunities costing your organization money?
<--- Score
9. What do you measure and why?
<--- Score
10. What are the strategic priorities for this year?
<--- Score
11. What are your key Information systems security engineering organizational performance measures, including key short and longer-term financial measures?
<--- Score
12. How can you measure the performance?
<--- Score
13. How do you verify performance?
<--- Score
14. What causes mismanagement?
<--- Score
15. How do your measurements capture actionable Information systems security engineering information for use in exceeding your customers expectations and securing your customers engagement?
<--- Score
16. Does a Information systems security engineering quantification method exist?
<--- Score
17. What causes investor action?
<--- Score
18. What is the root cause(s) of the problem?
<--- Score
19. How do you verify and develop ideas and innovations?
<--- Score