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