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.
