Score
11. How do you catch Map database management definition inconsistencies?
<--- Score
12. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
13. How are consistent Map database management definitions important?
<--- Score
14. Is there any additional Map database management definition of success?
<--- Score
15. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
16. What gets examined?
<--- Score
17. Has/have the customer(s) been identified?
<--- Score
18. Is the Map database management scope manageable?
<--- Score
19. Has the Map database management 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
20. Scope of sensitive information?
<--- Score
21. Are required metrics defined, what are they?
<--- Score
22. What information should you gather?
<--- Score
23. What are the tasks and definitions?
<--- Score
24. Do you have organizational privacy requirements?
<--- Score
25. Has your scope been defined?
<--- Score
26. What is the definition of Map database management excellence?
<--- Score
27. Who is gathering Map database management information?
<--- Score
28. How do you gather Map database management requirements?
<--- Score
29. What sort of initial information to gather?
<--- Score
30. Does the scope remain the same?
<--- Score
31. What are the rough order estimates on cost savings/opportunities that Map database management brings?
<--- Score
32. What critical content must be communicated – who, what, when, where, and how?
<--- Score
33. Are all requirements met?
<--- Score
34. What customer feedback methods were used to solicit their input?
<--- Score
35. What intelligence can you gather?
<--- Score
36. 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
37. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
38. If substitutes have been appointed, have they been briefed on the Map database management goals and received regular communications as to the progress to date?
<--- Score
39. What is the worst case scenario?
<--- Score
40. How do you build the right business case?
<--- Score
41. How do you hand over Map database management context?
<--- Score
42. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
43. What scope to assess?
<--- Score
44. 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
45. What are the core elements of the Map database management business case?
<--- Score
46. What system do you use for gathering Map database management information?
<--- Score
47. Where can you gather more information?
<--- Score
48. What key stakeholder process output measure(s) does Map database management leverage and how?
<--- Score
49. How do you gather requirements?
<--- Score
50. How and when will the baselines be defined?
<--- Score
51. How do you manage unclear Map database management requirements?
<--- Score
52. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
53. Has a Map database management requirement not been met?
<--- Score
54. What knowledge or experience is required?
<---
