Читать книгу Basic Email Security A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 8
ОглавлениеCRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
2. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
3. Is it clearly defined in and to your organization what you do?
<--- Score
4. Does the team have regular meetings?
<--- Score
5. What is out of scope?
<--- Score
6. What would be the goal or target for a Basic Email Security’s improvement team?
<--- Score
7. What sources do you use to gather information for a Basic Email Security study?
<--- Score
8. How have you defined all Basic Email Security requirements first?
<--- Score
9. Is the Basic Email Security scope manageable?
<--- Score
10. What is in scope?
<--- Score
11. Will team members perform Basic Email Security work when assigned and in a timely fashion?
<--- Score
12. How are consistent Basic Email Security definitions important?
<--- Score
13. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
14. What are the rough order estimates on cost savings/opportunities that Basic Email Security brings?
<--- Score
15. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
16. Will team members regularly document their Basic Email Security work?
<--- Score
17. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
18. What information do you gather?
<--- Score
19. What is the definition of Basic Email Security excellence?
<--- Score
20. How does the Basic Email Security manager ensure against scope creep?
<--- Score
21. Are task requirements clearly defined?
<--- Score
22. How will the Basic Email Security team and the group measure complete success of Basic Email Security?
<--- Score
23. What was the context?
<--- Score
24. Who is gathering information?
<--- Score
25. How would you define the culture at your organization, how susceptible is it to Basic Email Security changes?
<--- Score
26. Is the team equipped with available and reliable resources?
<--- Score
27. Who defines (or who defined) the rules and roles?
<--- Score
28. Is special Basic Email Security user knowledge required?
<--- Score
29. 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
30. Are required metrics defined, what are they?
<--- Score
31. Are audit criteria, scope, frequency and methods defined?
<--- Score
32. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
33. What is the context?
<--- Score
34. Has a team charter been developed and communicated?
<--- Score
35. How do you manage unclear Basic Email Security requirements?
<--- Score
36. Is the work to date meeting requirements?
<--- Score
37. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
38. Are the Basic Email Security requirements testable?
<--- Score
39. How is the team tracking and documenting its work?
<--- Score
40. Has your scope been defined?
<--- Score
41. 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
42. What are the dynamics of the communication plan?
<--- Score
43. What is the scope of the Basic Email Security effort?
<--- Score
44. What sort of initial information to gather?
<--- Score
45. What is out-of-scope initially?
<--- Score
46. What are (control) requirements for Basic Email Security Information?
<--- Score
47. Are customer(s) identified and segmented according to their different needs and requirements?
<--- Score
48. The political context: who holds power?
<--- Score
49. How do you hand over Basic Email Security context?
<--- Score
50. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
51. What is the scope of Basic Email Security?
<--- Score
52. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
53. What key stakeholder process output measure(s) does Basic Email Security leverage and how?
<--- Score
54. What constraints exist that might impact the team?
<--- Score
55. Has the Basic Email Security 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. What is the scope?
<--- Score
57. Is Basic Email Security required?
<--- Score
58. Who are the Basic Email Security improvement team members, including Management Leads and Coaches?
<--- Score
59. When is the estimated completion date?
<--- Score
60. What are the Basic Email Security tasks and definitions?
<--- Score
61. Is Basic Email Security linked to key stakeholder goals and objectives?
<--- Score
62. How do you manage scope?
<--- Score
63. What scope do you want your strategy to cover?
<--- Score
64. Will a Basic Email Security production readiness review be required?
<--- Score
65. What baselines are required to be defined and managed?
<--- Score
66. Have all of the relationships been defined properly?
<--- Score
67. Why are you doing Basic Email Security and what is the scope?
<--- Score
68. What customer feedback methods were used to solicit their input?
<--- Score
69. Who approved the Basic Email Security scope?
<--- Score
70. Do you have organizational privacy requirements?
<--- Score
71. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
72. What is the definition of success?
<--- Score
73. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
74. What is the worst case scenario?
<--- Score
75. What Basic Email Security requirements should be gathered?
<--- Score
76. How do you catch Basic Email Security definition inconsistencies?
<--- Score
77. What knowledge or experience is required?
<--- Score
78. Is the scope of Basic Email Security defined?
<--- Score
79. Does the scope remain the same?
<--- Score
80. Are improvement team members fully trained on Basic Email Security?
<--- Score
81. Is there a critical path to deliver Basic Email Security results?
<--- Score
82. Has/have the customer(s) been identified?
<--- Score
83. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
84. What gets examined?
<--- Score
85. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
86. Are accountability and ownership for Basic Email Security clearly defined?
<--- Score
87. What is in the scope and what is not in scope?
<--- Score
88. Who is gathering Basic Email Security information?
<--- Score
89. What are the core elements of the Basic Email Security business case?
<--- Score
90. How do you keep key subject matter experts in the loop?
<--- Score
91. What intelligence can you gather?
<--- Score
92. How would you define Basic Email Security leadership?
<--- Score
93. How will variation in the actual durations of each activity be dealt with to ensure that the expected Basic Email Security results are met?
<--- Score
94. What Basic Email Security services do you require?
<--- Score
95. Has a Basic Email Security requirement not been met?
<--- Score
96. How do you gather Basic Email Security requirements?
<--- Score
97. What critical content must be communicated – who, what, when, where, and how?
<--- Score
98. How did the Basic Email Security manager receive input to the development of a Basic Email Security improvement plan and 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 to the Basic Email Security Index at the beginning of the Self-Assessment.
