style="font-size:15px;"> 96. Are approval levels defined for contracts and supplements to contracts?
<--- Score
97. What is out-of-scope initially?
<--- Score
98. What sort of initial information to gather?
<--- Score
99. Is the team equipped with available and reliable resources?
<--- Score
100. Is there any additional Software Performance Engineering definition of success?
<--- Score
101. What information should you gather?
<--- Score
102. What is the scope of the Software Performance Engineering effort?
<--- Score
103. Is there a Software Performance Engineering management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
104. Are there different segments of customers?
<--- Score
105. What constraints exist that might impact the team?
<--- Score
106. How do you gather the stories?
<--- Score
107. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
108. What intelligence can you gather?
<--- Score
109. Is the work to date meeting requirements?
<--- Score
110. Is special Software Performance Engineering user knowledge required?
<--- Score
111. Why are you doing Software Performance Engineering and what is the scope?
<--- Score
112. What are the dynamics of the communication plan?
<--- Score
113. What are the compelling stakeholder reasons for embarking on Software Performance Engineering?
<--- Score
114. What is out of scope?
<--- Score
115. Is the scope of Software Performance Engineering defined?
<--- Score
116. What are the Software Performance Engineering tasks and definitions?
<--- Score
117. What are the rough order estimates on cost savings/opportunities that Software Performance Engineering brings?
<--- Score
118. How is the team tracking and documenting its work?
<--- Score
119. Do you all define Software Performance Engineering in the same way?
<--- Score
120. How often are the team meetings?
<--- Score
121. Will team members perform Software Performance Engineering work when assigned and in a timely fashion?
<--- Score
122. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
123. 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
124. How did the Software Performance Engineering manager receive input to the development of a Software Performance Engineering improvement plan and the estimated completion dates/times of each activity?
<--- Score
125. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
126. Are the Software Performance Engineering requirements testable?
<--- Score
127. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
128. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software Performance Engineering results are met?
<--- Score
129. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
130. What is the worst case scenario?
<--- Score
131. Do you have organizational privacy requirements?
<--- Score
132. Have specific policy objectives been defined?
<--- Score
133. What key stakeholder process output measure(s) does Software Performance Engineering leverage and how?
<--- Score
134. Has the Software Performance Engineering 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
135. What are the tasks and definitions?
<--- Score
136. Are accountability and ownership for Software Performance Engineering clearly defined?
<--- Score
137. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
