the estimated completion dates/times of each activity?
<--- Score
99. What are the tasks and definitions?
<--- Score
100. What are the compelling stakeholder reasons for embarking on Basic Email Security?
<--- Score
101. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
102. How often are the team meetings?
<--- Score
103. Is data collected and displayed to better understand customer(s) critical needs and requirements.
<--- Score
104. Are there different segments of customers?
<--- Score
105. Are approval levels defined for contracts and supplements to contracts?
<--- Score
106. Is there a Basic Email Security management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
107. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
108. Is scope creep really all bad news?
<--- Score
109. What information should you gather?
<--- Score
110. How do you gather requirements?
<--- Score
111. What scope to assess?
<--- Score
112. Have all basic functions of Basic Email Security been defined?
<--- Score
113. Scope of sensitive information?
<--- Score
114. 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
115. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
116. What are the requirements for audit information?
<--- Score
117. Do you all define Basic Email Security in the same way?
<--- Score
118. Are there any constraints known that bear on the ability to perform Basic Email Security work? How is the team addressing them?
<--- Score
119. Do you have a Basic Email Security success story or case study ready to tell and share?
<--- Score
120. What happens if Basic Email Security’s scope changes?
<--- Score
121. Are the Basic Email Security requirements complete?
<--- Score
122. How do you gather the stories?
<--- Score
123. Is there any additional Basic Email Security definition of success?
<--- Score
124. How do you build the right business case?
<--- Score
125. If substitutes have been appointed, have they been briefed on the Basic Email Security goals and received regular communications as to the progress to date?
<--- Score
126. How do you think the partners involved in Basic Email Security would have defined success?
<--- Score
127. How do you manage changes in Basic Email Security requirements?
<--- Score
128. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
129. When is/was the Basic Email Security start date?
<--- Score
130. What are the record-keeping requirements of Basic Email Security activities?
<--- Score
131. How and when will the baselines be defined?
<--- Score
132. What defines best in class?
<--- Score
133. Has the direction changed at all during the course of Basic Email Security? If so, when did it change and why?
<--- Score
134. Are all requirements met?
<--- Score
135. What are the Basic Email Security use cases?
<--- Score
136. Is Basic Email Security currently on schedule according to the plan?
<--- Score
137. Where can you gather more information?
<--- Score
138. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
139. Are roles and responsibilities formally defined?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score
