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