Читать книгу Ethereum Blockchain As A Service 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. Is there a Ethereum Blockchain as a Service management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?

<--- Score

2. What Ethereum Blockchain as a Service requirements should be gathered?

<--- Score

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

<--- Score

4. Is the work to date meeting requirements?

<--- Score

5. How have you defined all Ethereum Blockchain as a Service requirements first?

<--- Score

6. What system do you use for gathering Ethereum Blockchain as a Service information?

<--- Score

7. How do you hand over Ethereum Blockchain as a Service context?

<--- Score

8. Why are you doing Ethereum Blockchain as a Service and what is the scope?

<--- Score

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

<--- Score

10. What are the compelling stakeholder reasons for embarking on Ethereum Blockchain as a Service?

<--- Score

11. What knowledge or experience is required?

<--- Score

12. What is the context?

<--- Score

13. Has your scope been defined?

<--- Score

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

<--- Score

15. Who is gathering Ethereum Blockchain as a Service information?

<--- Score

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

17. Who are the Ethereum Blockchain as a Service improvement team members, including Management Leads and Coaches?

<--- Score

18. What scope to assess?

<--- Score

19. Is Ethereum Blockchain as a Service currently on schedule according to the plan?

<--- Score

20. Are accountability and ownership for Ethereum Blockchain as a Service clearly defined?

<--- Score

21. What is the worst case scenario?

<--- Score

22. How do you manage scope?

<--- Score

23. How do you gather the stories?

<--- Score

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

<--- Score

25. Do you all define Ethereum Blockchain as a Service in the same way?

<--- Score

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

<--- Score

27. What key stakeholder process output measure(s) does Ethereum Blockchain as a Service leverage and how?

<--- Score

28. Is Ethereum Blockchain as a Service required?

<--- Score

29. Is the Ethereum Blockchain as a Service scope manageable?

<--- Score

30. Is there a clear Ethereum Blockchain as a Service case definition?

<--- Score

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

<--- Score

32. Does the scope remain the same?

<--- Score

33. What are the core elements of the Ethereum Blockchain as a Service business case?

<--- Score

34. What are the dynamics of the communication plan?

<--- Score

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

<--- Score

36. Has the direction changed at all during the course of Ethereum Blockchain as a Service? If so, when did it change and why?

<--- Score

37. How often are the team meetings?

<--- Score

38. How can the value of Ethereum Blockchain as a Service be defined?

<--- Score

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

<--- Score

40. Is the scope of Ethereum Blockchain as a Service defined?

<--- Score

41. Has the Ethereum Blockchain as a Service 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. How do you catch Ethereum Blockchain as a Service definition inconsistencies?

<--- Score

43. What would be the goal or target for a Ethereum Blockchain as a Service’s improvement team?

<--- Score

44. What constraints exist that might impact the team?

<--- Score

45. What are the Ethereum Blockchain as a Service use cases?

<--- Score

46. What intelligence can you gather?

<--- Score

47. Have all basic functions of Ethereum Blockchain as a Service been defined?

<--- Score

48. What is in scope?

<--- Score

49. The political context: who holds power?

<--- Score

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

<--- Score

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

<--- Score

52. Has a Ethereum Blockchain as a Service requirement not been met?

<--- Score

53. Are resources adequate for the scope?

<--- Score

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

<--- Score

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

<--- Score

56. Are there different segments of customers?

<--- Score

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

<--- Score

58. How does the Ethereum Blockchain as a Service manager ensure against scope creep?

<--- Score

59. What Ethereum Blockchain as a Service services do you require?

<--- Score

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

<--- Score

61. Have all of the relationships been defined properly?

<--- Score

62. Do you have organizational privacy requirements?

<--- Score

63. Is scope creep really all bad news?

<--- Score

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

<--- Score

65. Has a team charter been developed and communicated?

<--- Score

66. Is Ethereum Blockchain as a Service linked to key stakeholder goals and objectives?

<--- Score

67. How will the Ethereum Blockchain as a Service team and the group measure complete success of Ethereum Blockchain as a Service?

<--- Score

68. When is the estimated completion date?

<--- Score

69. If substitutes have been appointed, have they been briefed on the Ethereum Blockchain as a Service goals and received regular communications as to the progress to date?

<--- Score

70. What sort of initial information to gather?

<--- Score

71. Are the Ethereum Blockchain as a Service requirements complete?

<--- Score

72. Scope of sensitive information?

<--- Score

73. Is there any additional Ethereum Blockchain as a Service definition of success?

<--- Score

74. What defines best in class?

<--- Score

75. How did the Ethereum Blockchain as a Service manager receive input to the development of a Ethereum Blockchain as a Service improvement plan and the estimated completion dates/times of each activity?

<--- Score

76. When is/was the Ethereum Blockchain as a Service start date?

<--- Score

77. What is out-of-scope initially?

<--- Score

78. Are there any constraints known that bear on the ability to perform Ethereum Blockchain as a Service work? How is the team addressing them?

<--- Score

79. Who approved the Ethereum Blockchain as a Service scope?

<--- Score

80. What is out of scope?

<--- Score

81. How do you think the partners involved in Ethereum Blockchain as a Service would have defined success?

<--- Score

82. Is special Ethereum Blockchain as a Service user knowledge required?

<--- Score

83. Are roles and responsibilities formally defined?

<--- Score

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

<--- Score

85. Do you have a Ethereum Blockchain as a Service success story or case study ready to tell and share?

<--- Score

86. What are the Ethereum Blockchain as a Service tasks and definitions?

<--- Score

87. How are consistent Ethereum Blockchain as a Service definitions important?

<--- Score

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

89. Are the Ethereum Blockchain as a Service requirements testable?

<--- Score

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

<--- Score

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

<--- Score

92. Does the team have regular meetings?

<--- Score

93. What are the rough order estimates on cost savings/opportunities that Ethereum Blockchain as a Service brings?

<--- Score

94. How do you build the right business case?

<--- Score

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

<--- Score

96. How would you define Ethereum Blockchain as a Service leadership?

<--- Score

97. How will variation in the actual durations of each activity be dealt with to ensure that the expected Ethereum Blockchain as a Service results are met?

<--- Score

98. What is the scope of Ethereum Blockchain as a Service?

<--- Score

99. Where can you gather more information?

<--- Score

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

101. What information should you gather?

<--- Score

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

<--- Score

103. Will a Ethereum Blockchain as a Service production readiness review be required?

<--- Score

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

<--- Score

105. What is the definition of success?

<--- Score

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

<--- Score

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

<--- Score

108. How and when will the baselines be defined?

<--- Score

109. How do you manage unclear Ethereum Blockchain as a Service requirements?

<--- Score

110. What are the record-keeping requirements of Ethereum Blockchain as a Service activities?

<--- Score

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

<--- Score

112. What gets examined?

<--- Score

113. What happens if Ethereum Blockchain as a Service’s scope changes?

<--- Score

114. How do you manage changes in Ethereum Blockchain as a Service requirements?

<--- Score

115. What are the tasks and definitions?

<--- Score

116. What is the scope of the Ethereum Blockchain as a Service effort?

<--- Score

117. Who is gathering information?

<--- Score

118. What information do you gather?

<--- Score

119. How do you gather requirements?

<--- Score

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

<--- Score

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

<--- Score

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

<--- Score

123. Are all requirements met?

<--- Score

124. What are (control) requirements for Ethereum Blockchain as a Service Information?

<--- Score

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

<--- Score

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

<--- Score

127. Is there a critical path to deliver Ethereum Blockchain as a Service results?

<--- Score

128. What is the definition of Ethereum Blockchain as a Service excellence?

<--- Score

129. How would you define the culture at your organization, how susceptible is it to Ethereum Blockchain as a Service changes?

<--- Score

130. What are the requirements for audit information?

<--- Score

131. Is the Ethereum Blockchain as a Service scope complete and appropriately sized?

<--- Score

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

<--- Score

133. How do you gather Ethereum Blockchain as a Service requirements?

<--- Score

134. Are task requirements clearly defined?

<--- Score

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

<--- Score

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

<--- Score

137. What is the scope of the Ethereum Blockchain as a Service work?

<--- 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 Ethereum Blockchain as a Service Index at the beginning of the Self-Assessment.

Ethereum Blockchain As A Service A Complete Guide - 2020 Edition

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