style="font-size:15px;"> 11. How do you manage unclear Blockchain as a service requirements?
<--- Score
12. Are task requirements clearly defined?
<--- Score
13. 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
14. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
15. What is the scope of the Blockchain as a service work?
<--- Score
16. Are there any constraints known that bear on the ability to perform Blockchain as a service work? How is the team addressing them?
<--- Score
17. What is out of scope?
<--- Score
18. Do you have organizational privacy requirements?
<--- Score
19. Has/have the customer(s) been identified?
<--- Score
20. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
21. What was the context?
<--- Score
22. Are audit criteria, scope, frequency and methods defined?
<--- Score
23. How do you build the right business case?
<--- Score
24. How would you define Blockchain as a service leadership?
<--- Score
25. How would you define the culture at your organization, how susceptible is it to Blockchain as a service changes?
<--- Score
26. Is there a clear Blockchain as a service case definition?
<--- Score
27. What Blockchain as a service requirements should be gathered?
<--- Score
28. What baselines are required to be defined and managed?
<--- Score
29. Has the 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
30. How do you gather requirements?
<--- Score
31. What is the worst case scenario?
<--- Score
32. How do you gather the stories?
<--- Score
33. Scope of sensitive information?
<--- Score
34. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
35. What intelligence can you gather?
<--- Score
36. What is the scope of the Blockchain as a service effort?
<--- Score
37. Have all basic functions of Blockchain as a service been defined?
<--- Score
38. What Blockchain as a service services do you require?
<--- Score
39. Is Blockchain as a service required?
<--- Score
40. Are approval levels defined for contracts and supplements to contracts?
<--- Score
41. Is it clearly defined in and to your organization what you do?
<--- Score
42. Is special Blockchain as a service user knowledge required?
<--- Score
43. How often are the team meetings?
<--- Score
44. What defines best in class?
<--- Score
45. Do you all define Blockchain as a service in the same way?
<--- Score
46. How do you manage changes in Blockchain as a service requirements?
<--- Score
47. What are the dynamics of the communication plan?
<--- Score
48. Who is gathering information?
<--- Score
49. Is the Blockchain as a service scope complete and appropriately sized?
<--- Score
50. What gets examined?
<--- Score
51. What critical content must be communicated – who, what, when, where, and how?
<--- Score
52. What happens if Blockchain as a service’s scope changes?
<--- Score
53. Has a Blockchain as a service requirement not been met?
<--- Score
54. Is there any additional Blockchain as a service definition of success?
<--- Score
55. When is/was the Blockchain as a service start date?
<--- Score
56. What are the requirements
