Читать книгу Map Database Management 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. Is it clearly defined in and to your organization what you do?
<--- Score
2. What is the scope?
<--- Score
3. What is the definition of success?
<--- Score
4. How did the Map database management manager receive input to the development of a Map database management improvement plan and the estimated completion dates/times of each activity?
<--- Score
5. How does the Map database management manager ensure against scope creep?
<--- Score
6. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
7. What constraints exist that might impact the team?
<--- Score
8. Who is gathering information?
<--- Score
9. Are accountability and ownership for Map database management clearly defined?
<--- Score
10. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- 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?
<--- Score
55. How is the team tracking and documenting its work?
<--- Score
56. What is a worst-case scenario for losses?
<--- Score
57. Are there different segments of customers?
<--- Score
58. Is the scope of Map database management defined?
<--- Score
59. Are roles and responsibilities formally defined?
<--- Score
60. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
61. What is in the scope and what is not in scope?
<--- Score
62. How have you defined all Map database management requirements first?
<--- Score
63. Who defines (or who defined) the rules and roles?
<--- Score
64. How will the Map database management team and the group measure complete success of Map database management?
<--- Score
65. Is Map database management linked to key stakeholder goals and objectives?
<--- Score
66. What is out of scope?
<--- Score
67. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
68. What are the requirements for audit information?
<--- Score
69. Are there any constraints known that bear on the ability to perform Map database management work? How is the team addressing them?
<--- Score
70. How do you manage scope?
<--- Score
71. What information do you gather?
<--- Score
72. Has the direction changed at all during the course of Map database management? If so, when did it change and why?
<--- Score
73. What is the scope of the Map database management effort?
<--- Score
74. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
75. How will variation in the actual durations of each activity be dealt with to ensure that the expected Map database management results are met?
<--- Score
76. When is/was the Map database management start date?
<--- Score
77. What are the dynamics of the communication plan?
<--- Score
78. Is special Map database management user knowledge required?
<--- Score
79. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
80. Have specific policy objectives been defined?
<--- Score
81. Do you all define Map database management in the same way?
<--- Score
82. What are (control) requirements for Map database management Information?
<--- Score
83. Are the Map database management requirements testable?
<--- Score
84. What was the context?
<--- Score
85. 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
86. How do you think the partners involved in Map database management would have defined success?
<--- Score
87. Have all basic functions of Map database management been defined?
<--- Score
88. Who approved the Map database management scope?
<--- Score
89. What is the scope of Map database management?
<--- Score
90. Are approval levels defined for contracts and supplements to contracts?
<--- Score
91. What Map database management services do you require?
<--- Score
92. What defines best in class?
<--- Score
93. Is there a clear Map database management case definition?
<--- Score
94. Is there a critical path to deliver Map database management results?
<--- Score
95. Is Map database management required?
<--- Score
96. What is the scope of the Map database management work?
<--- Score
97. How often are the team meetings?
<--- Score
98. Is the Map database management scope complete and appropriately sized?
<--- Score
99. Are audit criteria, scope, frequency and methods defined?
<--- Score
100. What is out-of-scope initially?
<--- Score
101. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
102. Are the Map database management requirements complete?
<--- Score
103. How do you keep key subject matter experts in the loop?
<--- Score
104. Who are the Map database management improvement team members, including Management Leads and Coaches?
<--- Score
105. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
106. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
107. Are resources adequate for the scope?
<--- Score
108. How do you gather the stories?
<--- Score
109. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
110. What scope do you want your strategy to cover?
<--- Score
111. How would you define Map database management leadership?
<--- Score
112. What would be the goal or target for a Map database management’s improvement team?
<--- Score
113. What baselines are required to be defined and managed?
<--- Score
114. What happens if Map database management’s scope changes?
<--- Score
115. Is the work to date meeting requirements?
<--- Score
116. Has a team charter been developed and communicated?
<--- Score
117. Will a Map database management production readiness review be required?
<--- Score
118. How would you define the culture at your organization, how susceptible is it to Map database management changes?
<--- Score
119. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
120. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
121. What sources do you use to gather information for a Map database management study?
<--- Score
122. Why are you doing Map database management and what is the scope?
<--- Score
123. Is Map database management currently on schedule according to the plan?
<--- Score
124. What is the context?
<--- Score
125. What are the compelling stakeholder reasons for embarking on Map database management?
<--- Score
126. Are task requirements clearly defined?
<--- Score
127. What are the Map database management use cases?
<--- Score
128. Does the team have regular meetings?
<--- Score
129. Have all of the relationships been defined properly?
<--- Score
130. When is the estimated completion date?
<--- Score
131. What are the record-keeping requirements of Map database management activities?
<--- Score
132. What is in scope?
<--- 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 Map database management Index at the beginning of the Self-Assessment.
