Score
102. What are the compelling stakeholder reasons for embarking on Healthcare software?
<--- Score
103. What are the Healthcare software use cases?
<--- Score
104. Have specific policy objectives been defined?
<--- Score
105. Is it clearly defined in and to your organization what you do?
<--- Score
106. Do you all define Healthcare software in the same way?
<--- Score
107. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
108. Is there a clear Healthcare software case definition?
<--- Score
109. What constraints exist that might impact the team?
<--- Score
110. Have all of the relationships been defined properly?
<--- Score
111. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
112. How do you think the partners involved in Healthcare software would have defined success?
<--- Score
113. Has/have the customer(s) been identified?
<--- Score
114. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
115. The political context: who holds power?
<--- Score
116. Are the Healthcare software requirements complete?
<--- Score
117. Will team members perform Healthcare software work when assigned and in a timely fashion?
<--- Score
118. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
119. What are the core elements of the Healthcare software business case?
<--- Score
120. Are the Healthcare software requirements testable?
<--- Score
121. What was the context?
<--- Score
122. How is the team tracking and documenting its work?
<--- Score
123. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
124. Does the team have regular meetings?
<--- Score
125. How do you catch Healthcare software definition inconsistencies?
<--- Score
126. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
127. Are there any constraints known that bear on the ability to perform Healthcare software work? How is the team addressing them?
<--- Score
128. What are the Healthcare software tasks and definitions?
<--- Score
129. Who is gathering Healthcare software information?
<--- Score
130. What are the requirements for audit information?
<--- Score
131. How do you gather the stories?
<--- Score
132. Is special Healthcare software user knowledge required?
<--- Score
133. 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
134. What scope do you want your strategy to cover?
<--- Score
135. How would you define Healthcare software leadership?
<--- Score
136. What is out-of-scope initially?
<--- Score
137. What defines best in class?
<--- Score
138. How would you define the culture at your organization, how susceptible is it to Healthcare software changes?
<--- Score
139. What critical content must be communicated – who, what, when, where, and how?
<--- Score
140. What key stakeholder process output measure(s) does Healthcare software leverage and how?
<--- 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 Healthcare software Index at the beginning of the Self-Assessment.
CRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance and evolution of the situation.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3
