Читать книгу Functional Database Model 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. Who is gathering Functional Database Model information?
<--- Score
2. What defines best in class?
<--- Score
3. Are there different segments of customers?
<--- Score
4. What scope do you want your strategy to cover?
<--- Score
5. What system do you use for gathering Functional Database Model information?
<--- Score
6. Why are you doing Functional Database Model and what is the scope?
<--- Score
7. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
8. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
9. Do you all define Functional Database Model in the same way?
<--- Score
10. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
11. What are the compelling stakeholder reasons for embarking on Functional Database Model?
<--- Score
12. What are the Functional Database Model use cases?
<--- Score
13. What is the scope of the Functional Database Model work?
<--- Score
14. What scope to assess?
<--- Score
15. What is in scope?
<--- Score
16. How do you manage scope?
<--- Score
17. What are the Functional Database Model tasks and definitions?
<--- Score
18. Are task requirements clearly defined?
<--- Score
19. Where can you gather more information?
<--- Score
20. Is there a clear Functional Database Model case definition?
<--- Score
21. When is/was the Functional Database Model start date?
<--- Score
22. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
23. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
24. What would be the goal or target for a Functional Database Model’s improvement team?
<--- Score
25. Is there a critical path to deliver Functional Database Model results?
<--- Score
26. Who are the Functional Database Model improvement team members, including Management Leads and Coaches?
<--- Score
27. How do you gather requirements?
<--- Score
28. How can the value of Functional Database Model be defined?
<--- Score
29. Are there any constraints known that bear on the ability to perform Functional Database Model work? How is the team addressing them?
<--- Score
30. Is scope creep really all bad news?
<--- Score
31. What sources do you use to gather information for a Functional Database Model study?
<--- Score
32. How is the team tracking and documenting its work?
<--- Score
33. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
34. What are the record-keeping requirements of Functional Database Model activities?
<--- Score
35. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
36. What is the worst case scenario?
<--- Score
37. What are the rough order estimates on cost savings/opportunities that Functional Database Model brings?
<--- Score
38. Has your scope been defined?
<--- Score
39. What Functional Database Model requirements should be gathered?
<--- Score
40. How do you manage unclear Functional Database Model requirements?
<--- Score
41. The political context: who holds power?
<--- Score
42. What knowledge or experience is required?
<--- Score
43. Is the scope of Functional Database Model defined?
<--- Score
44. Are resources adequate for the scope?
<--- Score
45. When is the estimated completion date?
<--- Score
46. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
47. Are the Functional Database Model requirements complete?
<--- Score
48. What sort of initial information to gather?
<--- Score
49. How do you catch Functional Database Model definition inconsistencies?
<--- Score
50. Has the direction changed at all during the course of Functional Database Model? If so, when did it change and why?
<--- Score
51. What are the core elements of the Functional Database Model business case?
<--- Score
52. What are the tasks and definitions?
<--- Score
53. What was the context?
<--- Score
54. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
55. Are required metrics defined, what are they?
<--- Score
56. Does the scope remain the same?
<--- Score
57. How and when will the baselines be defined?
<--- Score
58. Is the Functional Database Model scope complete and appropriately sized?
<--- Score
59. Scope of sensitive information?
<--- Score
60. Has/have the customer(s) been identified?
<--- Score
61. How will the Functional Database Model team and the group measure complete success of Functional Database Model?
<--- Score
62. What are (control) requirements for Functional Database Model Information?
<--- Score
63. Do you have organizational privacy requirements?
<--- Score
64. How would you define the culture at your organization, how susceptible is it to Functional Database Model changes?
<--- Score
65. How does the Functional Database Model manager ensure against scope creep?
<--- Score
66. What key stakeholder process output measure(s) does Functional Database Model leverage and how?
<--- Score
67. What intelligence can you gather?
<--- Score
68. Is Functional Database Model currently on schedule according to the plan?
<--- Score
69. Are roles and responsibilities formally defined?
<--- Score
70. 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
71. Is there a Functional Database Model management charter, including stakeholder case, problem and goal statements, scope, milestones, roles and responsibilities, communication plan?
<--- Score
72. Have all of the relationships been defined properly?
<--- Score
73. How are consistent Functional Database Model definitions important?
<--- Score
74. How do you keep key subject matter experts in the loop?
<--- Score
75. Is Functional Database Model required?
<--- Score
76. Has the Functional Database Model 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
77. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
78. Are all requirements met?
<--- Score
79. What gets examined?
<--- Score
80. What is a worst-case scenario for losses?
<--- Score
81. Is it clearly defined in and to your organization what you do?
<--- Score
82. What happens if Functional Database Model’s scope changes?
<--- Score
83. Is the Functional Database Model scope manageable?
<--- Score
84. Have all basic functions of Functional Database Model been defined?
<--- Score
85. What baselines are required to be defined and managed?
<--- Score
86. How do you gather the stories?
<--- Score
87. How would you define Functional Database Model leadership?
<--- Score
88. Are accountability and ownership for Functional Database Model clearly defined?
<--- Score
89. What is the definition of Functional Database Model excellence?
<--- Score
90. Are the Functional Database Model requirements testable?
<--- Score
91. If substitutes have been appointed, have they been briefed on the Functional Database Model goals and received regular communications as to the progress to date?
<--- Score
92. What critical content must be communicated – who, what, when, where, and how?
<--- Score
93. How will variation in the actual durations of each activity be dealt with to ensure that the expected Functional Database Model results are met?
<--- Score
94. Is there any additional Functional Database Model definition of success?
<--- Score
95. What constraints exist that might impact the team?
<--- Score
96. What is in the scope and what is not in scope?
<--- Score
97. What is out of scope?
<--- Score
98. Do you have a Functional Database Model success story or case study ready to tell and share?
<--- Score
99. Will a Functional Database Model production readiness review be required?
<--- Score
100. Who is gathering information?
<--- Score
101. How did the Functional Database Model manager receive input to the development of a Functional Database Model improvement plan and the estimated completion dates/times of each activity?
<--- Score
102. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
103. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
104. Who defines (or who defined) the rules and roles?
<--- Score
105. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
106. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
107. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
108. Are audit criteria, scope, frequency and methods defined?
<--- Score
109. Is Functional Database Model linked to key stakeholder goals and objectives?
<--- Score
110. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
111. What are the dynamics of the communication plan?
<--- Score
112. 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
113. Has a team charter been developed and communicated?
<--- Score
114. Does the team have regular meetings?
<--- Score
115. What information should you gather?
<--- Score
116. How often are the team meetings?
<--- Score
117. Have specific policy objectives been defined?
<--- Score
118. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
119. How have you defined all Functional Database Model requirements first?
<--- Score
120. What are the requirements for audit information?
<--- Score
121. Are approval levels defined for contracts and supplements to contracts?
<--- Score
122. How do you build the right business case?
<--- Score
123. What is the definition of success?
<--- Score
124. How do you gather Functional Database Model requirements?
<--- Score
125. 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
126. Is special Functional Database Model user knowledge required?
<--- Score
127. Has a Functional Database Model requirement not been met?
<--- Score
128. How do you manage changes in Functional Database Model requirements?
<--- Score
129. What Functional Database Model services do you require?
<--- Score
130. What is the context?
<--- Score
131. What customer feedback methods were used to solicit their input?
<--- Score
132. What is out-of-scope initially?
<--- 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 Functional Database Model Index at the beginning of the Self-Assessment.
