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?
