Software Reliability Testing A Complete Guide - 2020 Edition. Gerardus Blokdyk

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

      1. What could cause you to change course?

      <--- Score

      2. How do you verify and develop ideas and innovations?

      <--- Score

      3. What are hidden Software reliability testing quality costs?

      <--- Score

      4. What drives O&M cost?

      <--- Score

      5. Are the Software reliability testing benefits worth its costs?

      <--- Score

      6. How much does it cost?

      <--- Score

      7. How will effects be measured?

      <--- Score

      8. What could cause delays in the schedule?

      <--- Score

      9. Which costs should be taken into account?

      <--- Score

      10. What are the uncertainties surrounding estimates of impact?

      <--- Score

      11. What are you verifying?

      <--- Score

      12. What causes innovation to fail or succeed in your organization?

      <--- Score

      13. What would it cost to replace your technology?

      <--- Score

      14. Who should receive measurement reports?

      <--- Score

      15. What happens if cost savings do not materialize?

      <--- Score

      16. What is the cost of rework?

      <--- Score

      17. Have you included everything in your Software reliability testing cost models?

      <--- Score

      18. How are measurements made?

      <--- Score

      19. What are allowable costs?

      <--- Score

      20. What does losing customers cost your organization?

      <--- Score

      21. What is your Software reliability testing quality cost segregation study?

      <--- Score

      22. What relevant entities could be measured?

      <--- Score

      23. What does a Test Case verify?

      <--- Score

      24. How do you measure lifecycle phases?

      <--- Score

      25. Are the measurements objective?

      <--- Score

      26. How do you verify performance?

      <--- Score

      27. Why do you expend time and effort to implement measurement, for whom?

      <--- Score

      28. What harm might be caused?

      <--- Score

      29. Are actual costs in line with budgeted costs?

      <--- Score

      30. What do you measure and why?

      <--- Score

      31. How can you measure Software reliability testing in a systematic way?

      <--- Score

      32. How sensitive must the Software reliability testing strategy be to cost?

      <--- Score

      33. What are the strategic priorities for this year?

      <--- Score

      34. What can be used to verify compliance?

      <--- Score

      35. What are the costs of delaying Software reliability testing action?

      <---