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