11. Who is gathering Microsoft Office Mobile information?
<--- Score
12. How is the team tracking and documenting its work?
<--- Score
13. How do you build the right business case?
<--- Score
14. Do you all define Microsoft Office Mobile in the same way?
<--- Score
15. Where can you gather more information?
<--- Score
16. When are meeting minutes sent out? Who is on the distribution list?
<--- 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 is the worst case scenario?
<--- Score
19. How have you defined all Microsoft Office Mobile requirements first?
<--- Score
20. Do you have a Microsoft Office Mobile success story or case study ready to tell and share?
<--- Score
21. What knowledge or experience is required?
<--- Score
22. What key stakeholder process output measure(s) does Microsoft Office Mobile leverage and how?
<--- Score
23. Has/have the customer(s) been identified?
<--- Score
24. If substitutes have been appointed, have they been briefed on the Microsoft Office Mobile goals and received regular communications as to the progress to date?
<--- Score
25. Is the Microsoft Office Mobile scope complete and appropriately sized?
<--- Score
26. Have all basic functions of Microsoft Office Mobile been defined?
<--- Score
27. Is full participation by members in regularly held team meetings guaranteed?
<--- Score
28. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
29. Who are the Microsoft Office Mobile improvement team members, including Management Leads and Coaches?
<--- Score
30. How and when will the baselines be defined?
<--- Score
31. Are resources adequate for the scope?
<--- Score
32. Are there different segments of customers?
<--- Score
33. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
34. Is the team formed and are team leaders (Coaches and Management Leads) assigned?
<--- Score
35. Have specific policy objectives been defined?
<--- Score
36. Who approved the Microsoft Office Mobile scope?
<--- Score
37. Are approval levels defined for contracts and supplements to contracts?
<--- Score
38. How do you gather the stories?
<--- Score
39. What sort of initial information to gather?
<--- Score
40. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
41. Has a team charter been developed and communicated?
<--- Score
42. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
43. 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
44. What critical content must be communicated – who, what, when, where, and how?
<--- Score
45. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
46. How will variation in the actual durations of each activity be dealt with to ensure that the expected Microsoft Office Mobile results are met?
<--- Score
47. What are the rough order estimates on cost savings/opportunities that Microsoft Office Mobile brings?
<--- Score
48. Do you have organizational privacy requirements?
<--- Score
49. How does the Microsoft Office Mobile manager ensure against scope creep?
<--- Score
50. What are the core elements of the Microsoft Office Mobile business case?
<--- Score
51. What is the scope of Microsoft Office Mobile?
<--- Score
52. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
53. What are the compelling stakeholder reasons for embarking on Microsoft
