Score
100. Why are you doing Web information system and what is the scope?
<--- Score
101. Do you all define Web information system in the same way?
<--- Score
102. How would you define Web information system leadership?
<--- Score
103. Will a Web information system production readiness review be required?
<--- Score
104. How will variation in the actual durations of each activity be dealt with to ensure that the expected Web information system results are met?
<--- Score
105. How do you gather requirements?
<--- Score
106. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
107. How can the value of Web information system be defined?
<--- Score
108. Is special Web information system user knowledge required?
<--- Score
109. What defines best in class?
<--- Score
110. What are the requirements for audit information?
<--- Score
111. What critical content must be communicated – who, what, when, where, and how?
<--- Score
112. How did the Web information system manager receive input to the development of a Web information system improvement plan and the estimated completion dates/times of each activity?
<--- Score
113. What are the compelling stakeholder reasons for embarking on Web information system?
<--- Score
114. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
115. Is scope creep really all bad news?
<--- Score
116. Have all basic functions of Web information system been defined?
<--- Score
117. Is the Web information system scope complete and appropriately sized?
<--- Score
118. Has the Web information system 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
119. How would you define the culture at your organization, how susceptible is it to Web information system changes?
<--- Score
120. What knowledge or experience is required?
<--- Score
121. What sort of initial information to gather?
<--- Score
122. What customer feedback methods were used to solicit their input?
<--- Score
123. Have all of the relationships been defined properly?
<--- Score
124. Are there any constraints known that bear on the ability to perform Web information system work? How is the team addressing them?
<--- Score
125. What is the context?
<--- Score
126. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
127. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
128. How often are the team meetings?
<--- Score
129. What is out of scope?
<--- Score
130. Is there a critical path to deliver Web information system results?
<--- Score
131. How do you keep key subject matter experts in the loop?
<--- Score
132. 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
133. Are there different segments of customers?
<--- Score
134. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
135. Will team members regularly document their Web information system work?
<--- Score
136. What is the scope?
<--- Score
137. 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
138. Is the Web information system scope manageable?
<--- Score
139. What would be the goal or target for a Web information system’s improvement team?
<--- Score
140. Is Web information system required?
<--- Score
141. Are approval levels defined for contracts and supplements to contracts?
<--- Score
