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.
