team addressing them?
<--- Score
6. What information should you gather?
<--- Score
7. How do you gather requirements?
<--- Score
8. Are accountability and ownership for Microsoft Exchange Server clearly defined?
<--- Score
9. What are the record-keeping requirements of Microsoft Exchange Server activities?
<--- Score
10. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
11. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
12. What key stakeholder process output measure(s) does Microsoft Exchange Server leverage and how?
<--- Score
13. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
14. What are the Microsoft Exchange Server tasks and definitions?
<--- Score
15. What information do you gather?
<--- Score
16. How will the Microsoft Exchange Server team and the group measure complete success of Microsoft Exchange Server?
<--- Score
17. Is the scope of Microsoft Exchange Server defined?
<--- Score
18. How do you manage unclear Microsoft Exchange Server requirements?
<--- Score
19. Are audit criteria, scope, frequency and methods defined?
<--- Score
20. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
21. Where can you gather more information?
<--- Score
22. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
23. Are improvement team members fully trained on Microsoft Exchange Server?
<--- Score
24. What is in the scope and what is not in scope?
<--- Score
25. Does the team have regular meetings?
<--- Score
26. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
27. Who is gathering Microsoft Exchange Server information?
<--- Score
28. Has your scope been defined?
<--- Score
29. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
30. Does the scope remain the same?
<--- Score
31. Is there a critical path to deliver Microsoft Exchange Server results?
<--- Score
32. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
33. When is/was the Microsoft Exchange Server start date?
<--- Score
34. Are the Microsoft Exchange Server requirements testable?
<--- Score
35. How do you build the right business case?
<--- Score
36. What is the context?
<--- Score
37. What system do you use for gathering Microsoft Exchange Server information?
<--- Score
38. What is a worst-case scenario for losses?
<--- Score
39. What is the scope of the Microsoft Exchange Server effort?
<--- Score
40. Is the Microsoft Exchange Server scope manageable?
<--- Score
41. What are the tasks and definitions?
<--- Score
42. When is the estimated completion date?
<--- Score
43. Have all basic functions of Microsoft Exchange Server been defined?
<--- Score
44. How do you gather the stories?
<--- Score
45. Who are the Microsoft Exchange Server improvement team members, including Management Leads and Coaches?
<--- Score
46. How have you defined all Microsoft Exchange Server requirements first?
<--- Score
47. What knowledge or experience is required?
<--- Score
48. Who approved the Microsoft Exchange Server scope?
<--- Score
49. How would you define Microsoft Exchange Server leadership?
<--- Score
50. What is the worst case scenario?
<--- Score
51. How does the Microsoft Exchange Server manager ensure against scope creep?
<--- Score
52. Will team members regularly document their Microsoft Exchange Server work?
<--- Score
53. What customer feedback methods were used to solicit their input?
<--- Score
54. What critical content must be communicated – who, what, when, where, and how?
<--- Score
55. What happens if Microsoft Exchange Server’s scope changes?
<--- Score
56. Has the direction changed at all during the course of Microsoft Exchange Server? If so, when did it change and why?
<--- Score
57. Is there a Microsoft Exchange Server management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
58. Are all requirements met?
<--- Score
59. Is the work to date meeting requirements?
<--- Score
60. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
61. 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?
<---