Score
97. Is the team equipped with available and reliable resources?
<--- Score
98. 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
99. Are roles and responsibilities formally defined?
<--- Score
100. 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
101. How do you gather Software test engineering requirements?
<--- Score
102. Are there any constraints known that bear on the ability to perform Software test engineering work? How is the team addressing them?
<--- Score
103. How do you manage changes in Software test engineering requirements?
<--- Score
104. Are there different segments of customers?
<--- Score
105. When is/was the Software test engineering start date?
<--- Score
106. How does the Software test engineering manager ensure against scope creep?
<--- Score
107. How do you gather the stories?
<--- Score
108. Who are the Software test engineering improvement team members, including Management Leads and Coaches?
<--- Score
109. Who is gathering information?
<--- Score
110. How will the Software test engineering team and the group measure complete success of Software test engineering?
<--- Score
111. What are the record-keeping requirements of Software test engineering activities?
<--- Score
112. What Software test engineering requirements should be gathered?
<--- Score
113. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
114. How are consistent Software test engineering definitions important?
<--- Score
115. What intelligence can you gather?
<--- Score
116. Are all requirements met?
<--- Score
117. How and when will the baselines be defined?
<--- Score
118. Who approved the Software test engineering scope?
<--- Score
119. Is the work to date meeting requirements?
<--- Score
120. What are the core elements of the Software test engineering business case?
<--- Score
121. What information do you gather?
<--- Score
122. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
123. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
124. What is in the scope and what is not in scope?
<--- Score
125. How did the Software test engineering manager receive input to the development of a Software test engineering improvement plan and the estimated completion dates/times of each activity?
<--- Score
126. Is the scope of Software test engineering defined?
<--- Score
127. Who defines (or who defined) the rules and roles?
<--- Score
128. What are the dynamics of the communication plan?
<--- Score
129. Are task requirements clearly defined?
<--- Score
130. How would you define Software test engineering leadership?
<--- Score
131. Where can you gather more information?
<--- Score
132. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
133. What constraints exist that might impact the team?
<--- Score
134. What Software test engineering services do you require?
<--- Score
135. Does the scope remain the same?
<--- Score
136. Is Software test engineering linked to key stakeholder goals and objectives?
<--- Score
137. What scope do you want your strategy to cover?
<--- 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 Software test engineering Index at the beginning of the Self-Assessment.
