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.
CRITERION #3: MEASURE:
INTENT: Gather the correct data. Measure the current performance and evolution of the situation.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. When a disaster occurs, who gets priority?
<--- Score
2. Was a business case (cost/benefit) developed?
<--- Score
3. Are you aware of what could cause a problem?
<--- Score
4. What would it cost
