<--- Score
90. How will variation in the actual durations of each activity be dealt with to ensure that the expected Information systems security engineering results are met?
<--- Score
91. Are accountability and ownership for Information systems security engineering clearly defined?
<--- Score
92. Is the scope of Information systems security engineering defined?
<--- Score
93. What is the scope of the Information systems security engineering work?
<--- Score
94. How do you manage changes in Information systems security engineering requirements?
<--- Score
95. How have you defined all Information systems security engineering requirements first?
<--- Score
96. How did the Information systems security engineering manager receive input to the development of a Information systems security engineering improvement plan and the estimated completion dates/times of each activity?
<--- Score
97. Are there any constraints known that bear on the ability to perform Information systems security engineering work? How is the team addressing them?
<--- Score
98. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
99. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
100. What are the core elements of the Information systems security engineering business case?
<--- Score
101. What are the rough order estimates on cost savings/opportunities that Information systems security engineering brings?
<--- Score
102. How will the Information systems security engineering team and the group measure complete success of Information systems security engineering?
<--- Score
103. Are the Information systems security engineering requirements testable?
<--- 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)
