Читать книгу ELK Stack 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. Why are you doing ELK stack and what is the scope?
<--- Score
2. What are the requirements for audit information?
<--- Score
3. Is ELK stack currently on schedule according to the plan?
<--- Score
4. How does the ELK stack manager ensure against scope creep?
<--- Score
5. Who are the ELK stack improvement team members, including Management Leads and Coaches?
<--- Score
6. Are there any constraints known that bear on the ability to perform ELK stack work? How is the team addressing them?
<--- Score
7. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
8. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
9. The political context: who holds power?
<--- Score
10. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
11. Has your scope been defined?
<--- Score
12. Has/have the customer(s) been identified?
<--- Score
13. What critical content must be communicated – who, what, when, where, and how?
<--- Score
14. What scope do you want your strategy to cover?
<--- Score
15. What ELK stack requirements should be gathered?
<--- Score
16. How do you gather the stories?
<--- Score
17. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
18. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
19. Is the team equipped with available and reliable resources?
<--- Score
20. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
21. What happens if ELK stack’s scope changes?
<--- Score
22. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
23. Is there a clear ELK stack case definition?
<--- Score
24. Has the ELK stack 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
25. Is ELK stack linked to key stakeholder goals and objectives?
<--- Score
26. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
27. Does the team have regular meetings?
<--- Score
28. Will a ELK stack production readiness review be required?
<--- Score
29. What are the ELK stack use cases?
<--- Score
30. Are approval levels defined for contracts and supplements to contracts?
<--- Score
31. Will team members regularly document their ELK stack work?
<--- Score
32. When is the estimated completion date?
<--- Score
33. What system do you use for gathering ELK stack information?
<--- Score
34. How do you manage changes in ELK stack requirements?
<--- Score
35. What constraints exist that might impact the team?
<--- Score
36. How do you think the partners involved in ELK stack would have defined success?
<--- Score
37. Is there a critical path to deliver ELK stack results?
<--- Score
38. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
39. Are task requirements clearly defined?
<--- Score
40. How would you define the culture at your organization, how susceptible is it to ELK stack changes?
<--- Score
41. Who approved the ELK stack scope?
<--- Score
42. How do you keep key subject matter experts in the loop?
<--- Score
43. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
44. What are the core elements of the ELK stack business case?
<--- Score
45. Has the direction changed at all during the course of ELK stack? If so, when did it change and why?
<--- Score
46. Is the ELK stack scope complete and appropriately sized?
<--- Score
47. How do you gather requirements?
<--- Score
48. What is the definition of ELK stack excellence?
<--- Score
49. What knowledge or experience is required?
<--- Score
50. What information should you gather?
<--- Score
51. What defines best in class?
<--- Score
52. What are the tasks and definitions?
<--- Score
53. What is the worst case scenario?
<--- Score
54. Are there different segments of customers?
<--- Score
55. How have you defined all ELK stack requirements first?
<--- Score
56. What baselines are required to be defined and managed?
<--- Score
57. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
58. Have specific policy objectives been defined?
<--- Score
59. Has a team charter been developed and communicated?
<--- Score
60. What are the record-keeping requirements of ELK stack activities?
<--- Score
61. What would be the goal or target for a ELK stack’s improvement team?
<--- Score
62. How do you manage scope?
<--- Score
63. Are the ELK stack requirements complete?
<--- Score
64. What are the dynamics of the communication plan?
<--- Score
65. What are (control) requirements for ELK stack Information?
<--- Score
66. How do you gather ELK stack requirements?
<--- Score
67. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
68. Who defines (or who defined) the rules and roles?
<--- Score
69. What sources do you use to gather information for a ELK stack study?
<--- Score
70. How do you catch ELK stack definition inconsistencies?
<--- Score
71. What is the scope of the ELK stack work?
<--- Score
72. Do you have organizational privacy requirements?
<--- Score
73. Is scope creep really all bad news?
<--- Score
74. Are the ELK stack requirements testable?
<--- Score
75. Is the ELK stack scope manageable?
<--- Score
76. What is the definition of success?
<--- Score
77. What scope to assess?
<--- Score
78. What was the context?
<--- Score
79. If substitutes have been appointed, have they been briefed on the ELK stack goals and received regular communications as to the progress to date?
<--- Score
80. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
81. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
82. What is the scope of ELK stack?
<--- Score
83. What is the scope of the ELK stack effort?
<--- Score
84. Do you all define ELK stack in the same way?
<--- Score
85. Is there a ELK stack management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
86. Is the scope of ELK stack defined?
<--- Score
87. How will the ELK stack team and the group measure complete success of ELK stack?
<--- Score
88. What sort of initial information to gather?
<--- Score
89. What is in scope?
<--- Score
90. 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
91. What are the ELK stack tasks and definitions?
<--- Score
92. How is the team tracking and documenting its work?
<--- Score
93. What is out-of-scope initially?
<--- Score
94. When is/was the ELK stack start date?
<--- Score
95. What is the context?
<--- Score
96. What ELK stack services do you require?
<--- Score
97. Has a ELK stack requirement not been met?
<--- Score
98. Scope of sensitive information?
<--- Score
99. 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
100. How are consistent ELK stack definitions important?
<--- Score
101. Is it clearly defined in and to your organization what you do?
<--- Score
102. How do you hand over ELK stack context?
<--- Score
103. What customer feedback methods were used to solicit their input?
<--- Score
104. Are roles and responsibilities formally defined?
<--- Score
105. How will variation in the actual durations of each activity be dealt with to ensure that the expected ELK stack results are met?
<--- Score
106. Are accountability and ownership for ELK stack clearly defined?
<--- Score
107. How do you build the right business case?
<--- Score
108. Who is gathering ELK stack information?
<--- Score
109. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
110. Where can you gather more information?
<--- Score
111. How did the ELK stack manager receive input to the development of a ELK stack improvement plan and the estimated completion dates/times of each activity?
<--- Score
112. How do you manage unclear ELK stack requirements?
<--- Score
113. How often are the team meetings?
<--- Score
114. What is the scope?
<--- Score
115. What are the compelling stakeholder reasons for embarking on ELK stack?
<--- Score
116. What key stakeholder process output measure(s) does ELK stack leverage and how?
<--- Score
117. 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
118. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
119. What information do you gather?
<--- Score
120. Are resources adequate for the scope?
<--- Score
121. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
122. Have all basic functions of ELK stack been defined?
<--- Score
123. What gets examined?
<--- Score
124. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
125. Have all of the relationships been defined properly?
<--- Score
126. What are the rough order estimates on cost savings/opportunities that ELK stack brings?
<--- Score
127. What is a worst-case scenario for losses?
<--- Score
128. What intelligence can you gather?
<--- Score
129. How would you define ELK stack leadership?
<--- Score
130. What is out of scope?
<--- Score
131. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- 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 ELK stack Index at the beginning of the Self-Assessment.
