Are approval levels defined for contracts and supplements to contracts?
<--- Score
98. Are the Electronic system level requirements testable?
<--- Score
99. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
100. How would you define Electronic system level leadership?
<--- Score
101. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
102. What are the record-keeping requirements of Electronic system level activities?
<--- Score
103. How will variation in the actual durations of each activity be dealt with to ensure that the expected Electronic system level results are met?
<--- Score
104. What knowledge or experience is required?
<--- Score
105. When is/was the Electronic system level start date?
<--- Score
106. Has a Electronic system level requirement not been met?
<--- Score
107. What information do you gather?
<--- Score
108. Have specific policy objectives been defined?
<--- Score
109. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
110. How do you gather Electronic system level requirements?
<--- Score
111. How and when will the baselines be defined?
<--- Score
112. When is the estimated completion date?
<--- Score
113. Are audit criteria, scope, frequency and methods defined?
<--- Score
114. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
115. What would be the goal or target for a Electronic system level’s improvement team?
<--- Score
116. Are resources adequate for the scope?
<--- Score
117. How do you think the partners involved in Electronic system level would have defined success?
<--- Score
118. Where can you gather more information?
<--- Score
119. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
120. What system do you use for gathering Electronic system level information?
<--- Score
121. Is the team equipped with available and reliable resources?
<--- Score
122. Is there a clear Electronic system level case definition?
<--- Score
123. Is the Electronic system level scope manageable?
<--- Score
124. Will team members perform Electronic system level work when assigned and in a timely fashion?
<--- Score
125. Who is gathering information?
<--- Score
126. What is out-of-scope initially?
<--- Score
127. What is a worst-case scenario for losses?
<--- Score
128. What is the scope of Electronic system level?
<--- Score
129. Has the direction changed at all during the course of Electronic system level? If so, when did it change and why?
<--- Score
130. How are consistent Electronic system level definitions important?
<--- Score
131. What Electronic system level services do you require?
<--- Score
132. How do you manage changes in Electronic system level requirements?
<--- Score
133. How do you gather the stories?
<--- Score
134. What sort of initial information to gather?
<--- Score
135. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
136. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
137. What scope to assess?
<--- Score
138. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
139. What is the context?
<--- Score
140. What Electronic system level requirements should be gathered?
<--- Score
Add
