<--- Score
109. Is knowledge of EEE Parts Failure Modes Required To Build a Fault Tolerant System?
<--- Score
110. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
111. Is there a critical path to deliver Fault tolerant system results?
<--- Score
112. How do you gather the stories?
<--- Score
113. Is scope creep really all bad news?
<--- Score
114. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
115. Who defines (or who defined) the rules and roles?
<--- Score
116. Is there any additional Fault tolerant system definition of success?
<--- Score
117. What intelligence can you gather?
<--- Score
118. Do you have organizational privacy requirements?
<--- Score
119. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
120. Why are you doing Fault tolerant system and what is the scope?
<--- Score
121. What are the record-keeping requirements of Fault tolerant system activities?
<--- Score
122. Is Fault tolerant system required?
<--- Score
123. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
124. Has the direction changed at all during the course of Fault tolerant system? If so, when did it change and why?
<--- Score
125. How will the Fault tolerant system team and the group measure complete success of Fault tolerant system?
<--- Score
126. Have all basic functions of Fault tolerant system been defined?
<--- Score
127. What sources do you use to gather information for a Fault tolerant system study?
<--- Score
128. What critical content must be communicated – who, what, when, where, and how?
<--- Score
129. What constraints exist that might impact the team?
<--- Score
130. Is Fault tolerant system linked to key stakeholder goals and objectives?
<--- Score
131. How often are the team meetings?
<--- Score
132. What is the scope of Fault tolerant system?
<--- Score
133. What Fault tolerant system requirements should be gathered?
<--- Score
134. How do you manage unclear Fault tolerant system requirements?
<--- Score
135. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
136. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- 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 Fault tolerant system 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. How do you verify and develop ideas and innovations?
<--- Score
2. What does a Test Case verify?
<--- Score
3. How to cause the change?
<--- Score
4. What measurements are being captured?
<--- Score
5. How long to keep data and how to manage retention costs?
<--- Score
6. Are the measurements objective?
<--- Score
7. What is the Fault tolerant system business impact?
<--- Score
8. What could cause delays in the schedule?
<--- Score
9. What measurements are possible, practicable and meaningful?
<--- Score
10. When a disaster occurs, who gets priority?
<--- Score
11. What causes extra work or rework?
<--- Score
12.
