14. Who defines (or who defined) the rules and roles?
<--- Score
15. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
16. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
17. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
18. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
19. Has a team charter been developed and communicated?
<--- Score
20. Is there a critical path to deliver Healthcare software results?
<--- Score
21. How do you build the right business case?
<--- Score
22. 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
23. What is the scope of Healthcare software?
<--- Score
24. Is the team equipped with available and reliable resources?
<--- Score
25. Is there any additional Healthcare software definition of success?
<--- Score
26. Have all basic functions of Healthcare software been defined?
<--- Score
27. Who are the Healthcare software improvement team members, including Management Leads and Coaches?
<--- Score
28. What would be the goal or target for a Healthcare software’s improvement team?
<--- Score
29. What are (control) requirements for Healthcare software Information?
<--- Score
30. Does the scope remain the same?
<--- Score
31. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
32. What customer feedback methods were used to solicit their input?
<--- Score
33. What is out of scope?
<--- Score
34. What is a worst-case scenario for losses?
<--- Score
35. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
36. Is the Healthcare software scope manageable?
<--- Score
37. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
38. When is the estimated completion date?
<--- Score
39. What is the scope?
<--- Score
40. How are consistent Healthcare software definitions important?
<--- Score
41. What sources do you use to gather information for a Healthcare software study?
<--- Score
42. How can the value of Healthcare software be defined?
<--- Score
43. Are approval levels defined for contracts and supplements to contracts?
<--- Score
44. Is there a Healthcare software management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
45. What information do you gather?
<--- Score
46. Has the Healthcare software 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
47. How do you gather requirements?
<--- Score
48. Is Healthcare software required?
<--- Score
49. Has the direction changed at all during the course of Healthcare software? If so, when did it change and why?
<--- Score
50. What is in scope?
<--- Score
51. Is scope creep really all bad news?
<--- Score
52. How have you defined all Healthcare software requirements first?
<--- Score
53. What system do you use for gathering Healthcare software information?
<--- Score
54. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
55. Will team members regularly document their Healthcare software work?
<--- Score
56. Do you have organizational privacy requirements?
<--- Score
57.
