ELK Stack A Complete Guide - 2020 Edition. Gerardus Blokdyk

Чтение книги онлайн.

СКАЧАТЬ 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.

      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. What would be a real cause for concern?

      <--- Score

      2. Are there any easy-to-implement alternatives to ELK stack? Sometimes other solutions are available that do not require the cost implications of a full-blown project?

      <--- Score

      3. What are hidden ELK stack quality costs?

      <--- Score

      4. Why do the measurements/indicators matter?

      <--- Score

      5. How frequently do you track ELK stack measures?

      <--- Score

      6. Which measures and indicators matter?

      <--- Score

      7. Where can you go to verify the info?

      <--- Score

      8. What is the total cost related to deploying ELK stack, including any consulting or professional services?

      <--- Score

      9. Among the ELK stack product and service cost to be estimated, which is considered hardest to estimate?

      <--- Score

      10. What are you verifying?

      <--- Score

      11. Are you aware of what could cause a problem?

      <--- Score

      12. How do you aggregate measures across priorities?

      <--- Score

      13. Do you effectively measure and reward individual and team performance?

      <--- Score

      14. The approach of traditional ELK stack works for detail complexity but is focused on a systematic approach rather than an understanding of the nature of systems themselves, what approach will permit your organization to deal with the kind of unpredictable emergent behaviors that dynamic complexity can introduce?

      <--- СКАЧАТЬ