Диалог во времени. Жизнь и творчество А.П. Чехова. Отсутствует

Software reliability excellence?

      <--- Score

      125. What is the context?

      <--- Score

      126. When is/was the Software reliability start date?

      <--- Score

      127. What are the boundaries of the scope? What is in bounds and what is not? What is the start point? What is the stop point?

      <--- Score

      128. How do you manage scope?

      <--- Score

      129. Who are the Software reliability improvement team members, including Management Leads and Coaches?

      <--- Score

      130. What knowledge or experience is required?

      <--- Score

      131. Are approval levels defined for contracts and supplements to contracts?

      <--- Score

      132. Has everyone on the team, including the team leaders, been properly trained?

      <--- Score

      133. 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

      134. Is the Software reliability scope complete and appropriately sized?

      <--- Score

      135. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      136. In what way can you redefine the criteria of choice clients have in your category in your favor?

      <--- Score

      137. Will a Software reliability production readiness review be required?

      <--- Score

      138. What was the context?

      <--- 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 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 delays in the schedule?

      <--- Score

      2. How do you verify the authenticity of the data and information used?

      <--- Score

      3. At what cost?

      <--- Score

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

      <--- Score

      5. Are the Software reliability benefits worth its costs?

      <--- Score

      6. What measurements are being captured?

      <--- Score

      7. What are the estimated costs of proposed changes?

      <--- Score

      8. What causes investor action?

      <--- Score

      9. What is measured? Why?

      <--- Score

      10. When are costs are incurred?

      <--- Score

      11. How do you verify the Software reliability requirements quality?

      <--- Score

      12. What are your customers expectations and measures?

      <--- Score

      13. What are the operational costs after Software reliability deployment?

      <--- Score

      14. What harm might be caused?

      <--- Score

      15. Do you have any cost Software reliability limitation requirements?

      <--- Score

      16. Is the cost worth the Software reliability effort ?

      <--- Score

      17. What are the types and number of measures to use?

      <--- Score

      18. What drives O&M cost?

      <--- Score

      19. How do you verify your resources?

      <--- Score

      20. How is performance measured?

      <--- Score

      21. What do people want to verify?

      <--- Score

      22. What is the cause of any Software reliability gaps?

      <--- Score

      23. How will costs be allocated?

      <--- Score

      24. Do you have a flow diagram of what happens?

      <--- Score

      25. What are you verifying?

      <--- Score

      26. How frequently do you track Software reliability measures?

      <--- Score

      27. What relevant entities could be measured?

      <--- Score

      28. Does management have the right priorities among projects?

      <--- Score

      29. Where is the cost?

      <--- Score

      30. How can you manage cost down?

      <--- Score

      31. What are the costs?

      <--- Score

      32. Are Software reliability vulnerabilities categorized and prioritized?

      <--- Score

      33. Which Software reliability impacts are significant?

      <--- Score

      34. What does losing customers cost your organization?

      <--- Score

      35. What is your decision requirements diagram?

      <--- Score

      36. How will measures be used to manage and adapt?

      <--- Score

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

      <--- Score

      38. What are the uncertainties surrounding estimates of impact?

      <--- Score

      39. Among the Software reliability product and service cost to be estimated, which is considered hardest to estimate?

      <--- Score

      40. What causes extra work or rework?