68. What gets examined?
<--- Score
69. Is there a critical path to deliver Software reliability results?
<--- Score
70. Is special Software reliability user knowledge required?
<--- Score
71. How have you defined all Software reliability requirements first?
<--- Score
72. Is scope creep really all bad news?
<--- Score
73. How do you gather the stories?
<--- Score
74. How will variation in the actual durations of each activity be dealt with to ensure that the expected Software reliability results are met?
<--- Score
75. Is Software reliability required?
<--- Score
76. Is the Software reliability scope manageable?
<--- Score
77. What is the scope of the Software reliability work?
<--- Score
78. What scope to assess?
<--- Score
79. What constraints exist that might impact the team?
<--- Score
80. Is there a clear Software reliability case definition?
<--- Score
81. What are the requirements for audit information?
<--- Score
82. How is the team tracking and documenting its work?
<--- Score
83. Has/have the customer(s) been identified?
<--- Score
84. What are the dynamics of the communication plan?
<--- Score
85. What is the definition of success?
<--- Score
86. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
87. What are (control) requirements for Software reliability Information?
<--- Score
88. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
89. Who is gathering information?
<--- Score
90. What is in the scope and what is not in scope?
<--- Score
91. What is the worst case scenario?
<--- Score
92. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
93. What sort of initial information to gather?
<--- Score
94. How do you build the right business case?
<--- Score
95. What are the core elements of the Software reliability business case?
<--- Score
96. What is out of scope?
<--- Score
97. How would you define the culture at your organization, how susceptible is it to Software reliability changes?
<--- Score
98. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
99. Does the team have regular meetings?
<--- Score
100. Are accountability and ownership for Software reliability clearly defined?
<--- Score
101. How do you manage unclear Software reliability requirements?
<--- Score
102. Are there any constraints known that bear on the ability to perform Software reliability work? How is the team addressing them?
<--- Score
103. How do you keep key subject matter experts in the loop?
<--- Score
104. Where can you gather more information?
<--- Score
105. Why are you doing Software reliability and what is the scope?
<--- Score
106. Are required metrics defined, what are they?
<--- Score
107. What information do you gather?
<--- Score
108. How does the Software reliability manager ensure against scope creep?
<--- Score
109. What are the compelling stakeholder reasons for embarking on Software reliability?
<--- Score
110. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
111. Scope of sensitive information?
<--- Score
112. What is the scope of Software reliability?
<--- Score
113. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
114. Is Software reliability linked to key stakeholder goals and objectives?
<--- Score
115. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
116. Are roles and responsibilities formally defined?
<--- Score
117. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
118. What would be the goal or target for a Software reliability’s improvement team?
<--- Score
119. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
120. When is the estimated completion date?
<--- Score
121. 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
122. What is the scope of the Software reliability effort?
<--- Score
123. Has your scope been defined?
<--- Score
124. What is the definition of