Score
66. What Healthcare software services do you require?
<--- Score
67. What baselines are required to be defined and managed?
<--- Score
68. How do you keep key subject matter experts in the loop?
<--- Score
69. Has your scope been defined?
<--- Score
70. How do you manage scope?
<--- Score
71. Are improvement team members fully trained on Healthcare software?
<--- Score
72. Are team charters developed?
<--- Score
73. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
74. How often are the team meetings?
<--- Score
75. What gets examined?
<--- Score
76. How do you hand over Healthcare software context?
<--- Score
77. What is the scope of the Healthcare software work?
<--- Score
78. When is/was the Healthcare software start date?
<--- Score
79. Is Healthcare software currently on schedule according to the plan?
<--- Score
80. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
81. Are accountability and ownership for Healthcare software clearly defined?
<--- Score
82. Is the team sponsored by a champion or stakeholder leader?
<--- Score
83. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
84. How did the Healthcare software manager receive input to the development of a Healthcare software improvement plan and the estimated completion dates/times of each activity?
<--- Score
85. Is Healthcare software linked to key stakeholder goals and objectives?
<--- Score
86. What are the record-keeping requirements of Healthcare software activities?
<--- Score
87. If substitutes have been appointed, have they been briefed on the Healthcare software goals and received regular communications as to the progress to date?
<--- Score
88. Are there different segments of customers?
<--- Score
89. What information should you gather?
<--- Score
90. What sort of initial information to gather?
<--- Score
91. What is the worst case scenario?
<--- Score
92. How will the Healthcare software team and the group measure complete success of Healthcare software?
<--- Score
93. Are required metrics defined, what are they?
<--- Score
94. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
95. Is the work to date meeting requirements?
<--- Score
96. What is the context?
<--- Score
97. Are audit criteria, scope, frequency and methods defined?
<--- Score
98. How does the Healthcare software manager ensure against scope creep?
<--- Score
99. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
100. Are all requirements met?
<--- Score
101. How and when will the baselines be defined?
<--- 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?
<---