<--- Score
41. Which measures and indicators matter?
<--- Score
42. How to cause the change?
<--- Score
43. What evidence is there and what is measured?
<--- Score
44. How will success or failure be measured?
<--- Score
45. What are the Software reliability key cost drivers?
<--- Score
46. Are you taking your company in the direction of better and revenue or cheaper and cost?
<--- Score
47. What is the total cost related to deploying Software reliability, including any consulting or professional services?
<--- Score
48. Are supply costs steady or fluctuating?
<--- Score
49. Which costs should be taken into account?
<--- Score
50. How is progress measured?
<--- Score
51. What would be a real cause for concern?
<--- Score
52. Do you have an issue in getting priority?
<--- Score
53. What causes innovation to fail or succeed in your organization?
<--- Score
54. Why do the measurements/indicators matter?
<--- Score
55. When should you bother with diagrams?
<--- Score
56. How sensitive must the Software reliability strategy be to cost?
<--- Score
57. Are you aware of what could cause a problem?
<--- Score
58. What does a Test Case verify?
<--- Score
59. Are there measurements based on task performance?
<--- Score
60. How do you verify if Software reliability is built right?
<--- Score
61. How much does it cost?
<--- Score
62. Have design-to-cost goals been established?
<--- Score
63. What is the cost of rework?
<--- Score
64. What can be used to verify compliance?
<--- Score
65. How will effects be measured?
<--- Score
66. What are the costs and benefits?
<--- Score
67. Do you effectively measure and reward individual and team performance?
<--- Score
68. How do you measure lifecycle phases?
<--- Score
69. How do you measure variability?
<--- Score
70. How do you verify performance?
<--- Score
71. What are the costs of reform?
<--- Score
72. Have you included everything in your Software reliability cost models?
<--- Score
73. Where is it measured?
<--- Score
74. Do you verify that corrective actions were taken?
<--- Score
75. What are allowable costs?
<--- Score
76. How is the value delivered by Software reliability being measured?
<--- Score
77. What are your primary costs, revenues, assets?
<--- Score
78. Is there an opportunity to verify requirements?
<--- Score
79. How can you reduce the costs of obtaining inputs?
<--- Score
80. Is it feasible to quantify software reliability with reasonable confidence?
<--- Score
81. Did you tackle the cause or the symptom?
<--- Score
82. When a disaster occurs, who gets priority?
<--- Score
83. Are you able to realize any cost savings?
<--- Score
84. Have you made assumptions about the shape of the future, particularly its impact on your customers and competitors?
<--- Score
85. What are your operating costs?
<--- Score
86. What disadvantage does this cause for the user?
<--- Score
87. How can a Software reliability test verify your ideas or assumptions?
<--- Score
88. Does a Software reliability quantification method exist?
<--- Score
89. What methods are feasible and acceptable to estimate the impact of reforms?
<--- Score
90. Are actual costs in line with budgeted costs?
<--- Score
91. What could cause you to change course?
<--- Score
92. How do you verify and validate the Software reliability data?
<--- Score
93. What tests verify requirements?
<--- Score
94. What are hidden Software reliability quality costs?
<--- Score
95. Who is involved in verifying compliance?
<--- Score
96. Who should receive measurement reports?
<--- Score
97. Are the units of measure consistent?
<--- Score
98. What are the costs of delaying Software reliability action?
<--- Score
99. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Software reliability services/products?
<--- Score
100. What users will be impacted?
<--- Score
101. What are your key Software reliability organizational performance measures, including key short and longer-term financial measures?
<--- Score
102.