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
55. Has the Electronic system level 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
56. Are task requirements clearly defined?
<--- Score
57. Are accountability and ownership for Electronic system level clearly defined?
<--- Score
58. Are all requirements met?
<--- Score
59. How often are the team meetings?
<--- Score
60. Has your scope been defined?
<--- Score
61. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
62. Are there any constraints known that bear on the ability to perform Electronic system level work? How is the team addressing them?
<--- Score
63. Who defines (or who defined) the rules and roles?
<--- Score
64. What is the scope of the Electronic system level work?
<--- Score
65. Do you have a Electronic system level success story or case study ready to tell and share?
<--- Score
66. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
67. What sources do you use to gather information for a Electronic system level study?
<--- Score
68. Have all basic functions of Electronic system level been defined?
<--- Score
69. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
70. Do you all define Electronic system level in the same way?
<--- Score
71. Are there different segments of customers?
<--- Score
72. What baselines are required to be defined and managed?
<--- Score
73. What intelligence can you gather?
<--- Score
74. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
75. The political context: who holds power?
<--- Score
76. Is Electronic system level linked to key stakeholder goals and objectives?
<--- Score
77. How would you define the culture at your organization, how susceptible is it to Electronic system level changes?
<--- Score
78. What is the definition of Electronic system level excellence?
<--- Score
79. Are the Electronic system level requirements complete?
<--- Score
80. What defines best in class?
<--- Score
81. What critical content must be communicated – who, what, when, where, and how?
<--- Score
82. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
83. What are the Electronic system level tasks and definitions?
<--- Score
84. Who are the Electronic system level improvement team members, including Management Leads and Coaches?
<--- Score
85. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
86. Are roles and responsibilities formally defined?
<--- Score
87. Is special Electronic system level user knowledge required?
<--- Score
88. 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
89. How have you defined all Electronic system level requirements first?
<--- Score
90. How is the team tracking and documenting its work?
<--- Score
91. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
92. Scope of sensitive information?
<--- Score
93. Have all of the relationships been defined properly?
<--- Score
94. What are the Electronic system level use cases?
<--- Score
95. Why are you doing Electronic system level and what is the scope?
<--- Score
96. What is out of scope?
<--- Score
