a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
57. Is scope creep really all bad news?
<--- Score
58. Have all of the relationships been defined properly?
<--- Score
59. Are task requirements clearly defined?
<--- Score
60. What is the worst case scenario?
<--- Score
61. Are approval levels defined for contracts and supplements to contracts?
<--- Score
62. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
63. Who are the Public health information system improvement team members, including Management Leads and Coaches?
<--- Score
64. Why are you doing Public health information system and what is the scope?
<--- Score
65. Have specific policy objectives been defined?
<--- Score
66. What is in the scope and what is not in scope?
<--- Score
67. What critical content must be communicated – who, what, when, where, and how?
<--- Score
68. Is there any additional Public health information system definition of success?
<--- Score
69. How would you define the culture at your organization, how susceptible is it to Public health information system changes?
<--- Score
70. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
71. What Public health information system services do you require?
<--- Score
72. How does the Public health information system manager ensure against scope creep?
<--- Score
73. Have all basic functions of Public health information system been defined?
<--- Score
74. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
75. Has the Public health information system 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
76. How have you defined all Public health information system requirements first?
<--- Score
77. The political context: who holds power?
<--- 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. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
80. What are the compelling stakeholder reasons for embarking on Public health information system?
<--- Score
81. Is there a critical path to deliver Public health information system results?
<--- Score
82. Who is gathering Public health information system information?
<--- Score
83. How would you define Public health information system leadership?
<--- Score
84. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
85. How do you gather Public health information system requirements?
<--- Score
86. What happens if Public health information system’s scope changes?
<--- Score
87. What are the tasks and definitions?
<--- Score
88. Scope of sensitive information?
<--- Score
89. What scope do you want your strategy to cover?
<--- Score
90. What is the definition of success?
<--- Score
91. How do you keep key subject matter experts in the loop?
<--- Score
92. How do you manage changes in Public health information system requirements?
<--- Score
93. How do you think the partners involved in Public health information system would have defined success?
<--- Score
94. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
95. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
96. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
97. 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
