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
97. Are approval levels defined for contracts and supplements to contracts?
<--- Score
98. Are the Electronic system level requirements testable?
<--- Score
99. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
100. How would you define Electronic system level leadership?
<--- Score
101. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
102. What are the record-keeping requirements of Electronic system level activities?
<--- Score
103. How will variation in the actual durations of each activity be dealt with to ensure that the expected Electronic system level results are met?
<--- Score
104. What knowledge or experience is required?
<--- Score
105. When is/was the Electronic system level start date?
<--- Score
106. Has a Electronic system level requirement not been met?
<--- Score
107. What information do you gather?
<--- Score
108. Have specific policy objectives been defined?
<--- Score
109. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
110. How do you gather Electronic system level requirements?
<--- Score
111. How and when will the baselines be defined?
<--- Score
112. When is the estimated completion date?
<--- Score
113. Are audit criteria, scope, frequency and methods defined?
<--- Score
114. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
115. What would be the goal or target for a Electronic system level’s improvement team?
<--- Score
116. Are resources adequate for the scope?
<---