‘as is’ process map been completed, verified and validated?
<--- Score
102. Is it clearly defined in and to your organization what you do?
<--- Score
103. What Software reliability testing requirements should be gathered?
<--- Score
104. What knowledge or experience is required?
<--- Score
105. Scope of sensitive information?
<--- Score
106. Who are the Software reliability testing improvement team members, including Management Leads and Coaches?
<--- Score
107. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software reliability testing results are met?
<--- Score
108. If substitutes have been appointed, have they been briefed on the Software reliability testing goals and received regular communications as to the progress to date?
<--- Score
109. Who approved the Software reliability testing scope?
<--- Score
110. Have all of the relationships been defined properly?
<--- Score
111. Who is gathering Software reliability testing information?
<--- Score
112. What are the record-keeping requirements of Software reliability testing activities?
<--- Score
113. Have specific policy objectives been defined?
<--- Score
114. Do you have a Software reliability testing success story or case study ready to tell and share?
<--- Score
115. Is there any additional Software reliability testing definition of success?
<--- Score
116. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
117. Has a team charter been developed and communicated?
<--- Score
118. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
119. What are the dynamics of the communication plan?
<--- Score
120. Have all basic functions of Software reliability testing been defined?
<--- Score
121. What key stakeholder process output measure(s) does Software reliability testing leverage and how?
<--- Score
122. What are the rough order estimates on cost savings/opportunities that Software reliability testing brings?
<--- Score
123. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
124. What customer feedback methods were used to solicit their input?
<--- Score
125. Are all requirements met?
<--- Score
126. How have you defined all Software reliability testing requirements first?
<--- Score
127. How can the value of Software reliability testing be defined?
<--- Score
128. What is the definition of Software reliability testing excellence?
<--- Score
129. Are there different segments of customers?
<--- Score
130. 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
131. How do you keep key subject matter experts in the loop?
<--- Score
132. How do you think the partners involved in Software reliability testing would have defined success?
<--- Score
133. What sort of initial information to gather?
<--- Score
134. How is the team tracking and documenting its work?
<--- Score
135. How will the Software reliability testing team and the group measure complete success of Software reliability testing?
<--- Score
136. Is the Software reliability testing scope complete and appropriately sized?
<--- Score
137. Is the Software reliability testing scope manageable?
<--- 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 reliability testing 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
