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