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
