Читать книгу Fault Isolation 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. Are the Fault isolation requirements complete?

<--- Score

2. Is the team equipped with available and reliable resources?

<--- Score

3. Is scope creep really all bad news?

<--- Score

4. What knowledge or experience is required?

<--- Score

5. Where can you gather more information?

<--- Score

6. Does the scope remain the same?

<--- Score

7. Does the team have regular meetings?

<--- Score

8. How do you gather the stories?

<--- Score

9. What is the worst case scenario?

<--- Score

10. What is a worst-case scenario for losses?

<--- Score

11. What happens if Fault isolation’s scope changes?

<--- Score

12. Is Fault isolation required?

<--- Score

13. How and when will the baselines be defined?

<--- Score

14. What information do you gather?

<--- Score

15. Is the Fault isolation scope complete and appropriately sized?

<--- Score

16. What are the record-keeping requirements of Fault isolation activities?

<--- Score

17. How will variation in the actual durations of each activity be dealt with to ensure that the expected Fault isolation results are met?

<--- Score

18. Do you have a Fault isolation success story or case study ready to tell and share?

<--- Score

19. Have the customer needs been translated into specific, measurable requirements? How?

<--- Score

20. What are the rough order estimates on cost savings/opportunities that Fault isolation brings?

<--- Score

21. Is there a critical path to deliver Fault isolation results?

<--- Score

22. 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

23. What gets examined?

<--- Score

24. Are audit criteria, scope, frequency and methods defined?

<--- Score

25. What is out of scope?

<--- Score

26. Is it clearly defined in and to your organization what you do?

<--- Score

27. What Fault isolation services do you require?

<--- Score

28. Who are the Fault isolation improvement team members, including Management Leads and Coaches?

<--- Score

29. How do you manage changes in Fault isolation requirements?

<--- Score

30. Has a team charter been developed and communicated?

<--- Score

31. What are the dynamics of the communication plan?

<--- Score

32. How would you define the culture at your organization, how susceptible is it to Fault isolation changes?

<--- Score

33. Are task requirements clearly defined?

<--- Score

34. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

<--- Score

35. Do you all define Fault isolation in the same way?

<--- Score

36. Who approved the Fault isolation scope?

<--- Score

37. What is the definition of success?

<--- Score

38. Is the Fault isolation scope manageable?

<--- Score

39. Are required metrics defined, what are they?

<--- Score

40. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

<--- Score

41. Has the Fault isolation 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

42. Who defines (or who defined) the rules and roles?

<--- Score

43. Is there a clear Fault isolation case definition?

<--- Score

44. Is Fault isolation linked to key stakeholder goals and objectives?

<--- Score

45. How can the value of Fault isolation be defined?

<--- Score

46. Are approval levels defined for contracts and supplements to contracts?

<--- Score

47. What are the tasks and definitions?

<--- Score

48. Are accountability and ownership for Fault isolation clearly defined?

<--- Score

49. Do you have organizational privacy requirements?

<--- Score

50. Will team members regularly document their Fault isolation work?

<--- Score

51. Is data collected and displayed to better understand customer(s) critical needs and requirements.

<--- Score

52. How do you think the partners involved in Fault isolation would have defined success?

<--- Score

53. Are roles and responsibilities formally defined?

<--- Score

54. How does the Fault isolation manager ensure against scope creep?

<--- Score

55. Is the scope of Fault isolation defined?

<--- Score

56. If substitutes have been appointed, have they been briefed on the Fault isolation goals and received regular communications as to the progress to date?

<--- Score

57. What Fault isolation requirements should be gathered?

<--- Score

58. Are resources adequate for the scope?

<--- Score

59. What is the scope?

<--- Score

60. When are meeting minutes sent out? Who is on the distribution list?

<--- Score

61. When is/was the Fault isolation start date?

<--- Score

62. Who is gathering Fault isolation information?

<--- Score

63. Is Fault isolation currently on schedule according to the plan?

<--- Score

64. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

<--- Score

65. Has/have the customer(s) been identified?

<--- Score

66. What are (control) requirements for Fault isolation Information?

<--- Score

67. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

<--- Score

68. Are there any constraints known that bear on the ability to perform Fault isolation work? How is the team addressing them?

<--- Score

69. Are the Fault isolation requirements testable?

<--- Score

70. When is the estimated completion date?

<--- Score

71. What scope do you want your strategy to cover?

<--- Score

72. How would you define Fault isolation leadership?

<--- Score

73. Will a Fault isolation production readiness review be required?

<--- Score

74. What defines best in class?

<--- Score

75. What are the compelling stakeholder reasons for embarking on Fault isolation?

<--- Score

76. What is the definition of Fault isolation excellence?

<--- Score

77. Are there different segments of customers?

<--- Score

78. How often are the team meetings?

<--- Score

79. What is the scope of Fault isolation?

<--- Score

80. In what way can you redefine the criteria of choice clients have in your category in your favor?

<--- Score

81. How do you hand over Fault isolation context?

<--- Score

82. 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

83. How do you keep key subject matter experts in the loop?

<--- Score

84. What key stakeholder process output measure(s) does Fault isolation leverage and how?

<--- Score

85. Has everyone on the team, including the team leaders, been properly trained?

<--- Score

86. How do you gather Fault isolation requirements?

<--- Score

87. 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

88. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

<--- Score

89. How will the Fault isolation team and the group measure complete success of Fault isolation?

<--- Score

90. How do you manage scope?

<--- Score

91. Has a high-level ‘as is’ process map been completed, verified and validated?

<--- Score

92. What is in the scope and what is not in scope?

<--- Score

93. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?

<--- Score

94. Are all requirements met?

<--- Score

95. What is out-of-scope initially?

<--- Score

96. What critical content must be communicated – who, what, when, where, and how?

<--- Score

97. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?

<--- Score

98. How is the team tracking and documenting its work?

<--- Score

99. What is in scope?

<--- Score

100. What system do you use for gathering Fault isolation information?

<--- Score

101. Is the current ‘as is’ process being followed? If not, what are the discrepancies?

<--- Score

102. Has your scope been defined?

<--- Score

103. Will team members perform Fault isolation work when assigned and in a timely fashion?

<--- Score

104. What is the scope of the Fault isolation work?

<--- Score

105. Scope of sensitive information?

<--- Score

106. How do you catch Fault isolation definition inconsistencies?

<--- Score

107. Is the work to date meeting requirements?

<--- Score

108. Have all basic functions of Fault isolation been defined?

<--- Score

109. Is special Fault isolation user knowledge required?

<--- Score

110. What is the context?

<--- Score

111. What are the Fault isolation tasks and definitions?

<--- Score

112. What sort of initial information to gather?

<--- Score

113. What scope to assess?

<--- Score

114. Are different versions of process maps needed to account for the different types of inputs?

<--- Score

115. What customer feedback methods were used to solicit their input?

<--- Score

116. Why are you doing Fault isolation and what is the scope?

<--- Score

117. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

<--- Score

118. What baselines are required to be defined and managed?

<--- Score

119. Is there any additional Fault isolation definition of success?

<--- Score

120. What was the context?

<--- Score

121. How was the ‘as is’ process map developed, reviewed, verified and validated?

<--- Score

122. Has the direction changed at all during the course of Fault isolation? If so, when did it change and why?

<--- Score

123. How do you build the right business case?

<--- Score

124. The political context: who holds power?

<--- Score

125. Have all of the relationships been defined properly?

<--- Score

126. Has a Fault isolation requirement not been met?

<--- Score

127. How did the Fault isolation manager receive input to the development of a Fault isolation improvement plan and the estimated completion dates/times of each activity?

<--- Score

128. What sources do you use to gather information for a Fault isolation study?

<--- Score

129. How do you manage unclear Fault isolation requirements?

<--- Score

130. What are the Fault isolation use cases?

<--- Score

131. What are the requirements for audit information?

<--- Score

132. What is the scope of the Fault isolation effort?

<--- Score

133. Are customer(s) identified and segmented according to their different needs and requirements?

<--- Score

134. Is there a Fault isolation management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

<--- Score

135. Has a project plan, Gantt chart, or similar been developed/completed?

<--- Score

136. What would be the goal or target for a Fault isolation’s improvement team?

<--- Score

137. How do you gather requirements?

<--- Score

138. How are consistent Fault isolation definitions important?

<--- Score

139. What constraints exist that might impact the team?

<--- Score

140. What intelligence can you gather?

<--- Score

141. What are the core elements of the Fault isolation business case?

<--- 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 isolation Index at the beginning of the Self-Assessment.

Fault Isolation A Complete Guide - 2020 Edition

Подняться наверх