Читать книгу Fault Tolerant System A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8
ОглавлениеCRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Who approved the Fault tolerant system scope?
<--- Score
2. Is the scope of Fault tolerant system defined?
<--- Score
3. What information do you gather?
<--- Score
4. When is the estimated completion date?
<--- Score
5. Are task requirements clearly defined?
<--- Score
6. 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
7. How do you manage changes in Fault tolerant system requirements?
<--- Score
8. What is the scope?
<--- Score
9. Do you have a Fault tolerant system success story or case study ready to tell and share?
<--- Score
10. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
11. Is it clearly defined in and to your organization what you do?
<--- Score
12. 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
13. Are there any constraints known that bear on the ability to perform Fault tolerant system work? How is the team addressing them?
<--- Score
14. What is the scope of the Fault tolerant system work?
<--- Score
15. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
16. How have you defined all Fault tolerant system requirements first?
<--- Score
17. What is the worst case scenario?
<--- Score
18. Scope of sensitive information?
<--- Score
19. Is the Fault tolerant system scope complete and appropriately sized?
<--- Score
20. Are required metrics defined, what are they?
<--- Score
21. Will a Fault tolerant system production readiness review be required?
<--- Score
22. Is obsolescence of EEE Parts Failure Modes Required To Build a Fault Tolerant System?
<--- Score
23. How can the value of Fault tolerant system be defined?
<--- Score
24. How did the Fault tolerant system manager receive input to the development of a Fault tolerant system improvement plan and the estimated completion dates/times of each activity?
<--- Score
25. Are approval levels defined for contracts and supplements to contracts?
<--- Score
26. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
27. What are the Fault tolerant system use cases?
<--- Score
28. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
29. Does the scope remain the same?
<--- Score
30. What happens if Fault tolerant system’s scope changes?
<--- Score
31. What are the requirements for audit information?
<--- Score
32. What sort of initial information to gather?
<--- Score
33. What gets examined?
<--- Score
34. What is the definition of Fault tolerant system excellence?
<--- Score
35. How do you keep key subject matter experts in the loop?
<--- Score
36. Is the work to date meeting requirements?
<--- Score
37. What information should you gather?
<--- Score
38. What are the dependability requirements of fault tolerant system?
<--- Score
39. What is the context?
<--- Score
40. How will variation in the actual durations of each activity be dealt with to ensure that the expected Fault tolerant system results are met?
<--- Score
41. Is there a clear Fault tolerant system case definition?
<--- Score
42. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
43. Who are the Fault tolerant system improvement team members, including Management Leads and Coaches?
<--- Score
44. Are roles and responsibilities formally defined?
<--- Score
45. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
46. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
47. Have specific policy objectives been defined?
<--- Score
48. What key stakeholder process output measure(s) does Fault tolerant system leverage and how?
<--- Score
49. How do you catch Fault tolerant system definition inconsistencies?
<--- Score
50. What would be the goal or target for a Fault tolerant system’s improvement team?
<--- Score
51. Are resources adequate for the scope?
<--- Score
52. What are the compelling stakeholder reasons for embarking on Fault tolerant system?
<--- Score
53. Do you all define Fault tolerant system in the same way?
<--- Score
54. The political context: who holds power?
<--- Score
55. What is in scope?
<--- Score
56. Who is gathering information?
<--- Score
57. What are the tasks and definitions?
<--- Score
58. How do you manage scope?
<--- Score
59. How would you define the culture at your organization, how susceptible is it to Fault tolerant system changes?
<--- Score
60. How do you think the partners involved in Fault tolerant system would have defined success?
<--- Score
61. Has your scope been defined?
<--- Score
62. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
63. Has a Fault tolerant system requirement not been met?
<--- Score
64. Who is gathering Fault tolerant system information?
<--- Score
65. How are consistent Fault tolerant system definitions important?
<--- Score
66. Are audit criteria, scope, frequency and methods defined?
<--- Score
67. What is out-of-scope initially?
<--- Score
68. What are (control) requirements for Fault tolerant system Information?
<--- Score
69. What customer feedback methods were used to solicit their input?
<--- Score
70. What are the dynamics of the communication plan?
<--- Score
71. Has a team charter been developed and communicated?
<--- Score
72. Where can you gather more information?
<--- Score
73. What system do you use for gathering Fault tolerant system information?
<--- Score
74. When is/was the Fault tolerant system start date?
<--- Score
75. Are the Fault tolerant system requirements complete?
<--- Score
76. Are all requirements met?
<--- Score
77. How and when will the baselines be defined?
<--- Score
78. How do you gather requirements?
<--- Score
79. How do you gather Fault tolerant system requirements?
<--- Score
80. How do you build the right business case?
<--- Score
81. Does the team have regular meetings?
<--- Score
82. What is the definition of success?
<--- Score
83. Is special Fault tolerant system user knowledge required?
<--- Score
84. Is Fault tolerant system currently on schedule according to the plan?
<--- Score
85. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
86. Has/have the customer(s) been identified?
<--- Score
87. How is the team tracking and documenting its work?
<--- Score
88. If substitutes have been appointed, have they been briefed on the Fault tolerant system goals and received regular communications as to the progress to date?
<--- Score
89. What defines best in class?
<--- Score
90. What is out of scope?
<--- Score
91. How would you define Fault tolerant system leadership?
<--- Score
92. What scope do you want your strategy to cover?
<--- Score
93. What is a worst-case scenario for losses?
<--- Score
94. Are accountability and ownership for Fault tolerant system clearly defined?
<--- Score
95. Have all of the relationships been defined properly?
<--- Score
96. What are the rough order estimates on cost savings/opportunities that Fault tolerant system brings?
<--- Score
97. What knowledge or experience is required?
<--- Score
98. Is the Fault tolerant system scope manageable?
<--- Score
99. What Fault tolerant system services do you require?
<--- Score
100. 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
101. How does the Fault tolerant system manager ensure against scope creep?
<--- Score
102. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
103. What was the context?
<--- Score
104. What is the scope of the Fault tolerant system effort?
<--- Score
105. How do you hand over Fault tolerant system context?
<--- Score
106. Has the Fault tolerant system work been fairly and/or equitably divided and delegated among team members who are qualified and capable to perform the work? Has everyone contributed?
<--- Score
107. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
108. Are there different segments of customers?
<--- 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.
