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?
