<--- Score
71. Is scope creep really all bad news?
<--- Score
72. What Revenue Analytics services do you require?
<--- Score
73. How do you gather requirements?
<--- Score
74. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
75. Are audit criteria, scope, frequency and methods defined?
<--- Score
76. Are resources adequate for the scope?
<--- Score
77. Have all of the relationships been defined properly?
<--- Score
78. Will a Revenue Analytics production readiness review be required?
<--- Score
79. Is Revenue Analytics currently on schedule according to the plan?
<--- Score
80. What Revenue Analytics requirements should be gathered?
<--- Score
81. Have specific policy objectives been defined?
<--- Score
82. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
83. How do you keep key subject matter experts in the loop?
<--- Score
84. How will the Revenue Analytics team and the group measure complete success of Revenue Analytics?
<--- Score
85. Has the Revenue Analytics 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
86. What are the compelling stakeholder reasons for embarking on Revenue Analytics?
<--- Score
87. Who are the Revenue Analytics improvement team members, including Management Leads and Coaches?
<--- Score
88. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
89. How do you manage scope?
<--- Score
90. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
91. Do you have organizational privacy requirements?
<--- Score
92. When is/was the Revenue Analytics start date?
<--- Score
93. What baselines are required to be defined and managed?
<--- Score
94. What customer feedback methods were used to solicit their input?
<--- Score
95. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
96. Do you have a Revenue Analytics success story or case study ready to tell and share?
<--- Score
97. Is the Revenue Analytics scope complete and appropriately sized?
<--- Score
98. How and when will the baselines be defined?
<--- Score
99. Are different versions of process maps needed to account for the different types of inputs?
<--- Score
100. How do you manage unclear Revenue Analytics requirements?
<--- Score
101. Are approval levels defined for contracts and supplements to contracts?
<--- Score
102. Who is gathering Revenue Analytics information?
<--- Score
103. How do you manage changes in Revenue Analytics requirements?
<--- Score
104. Is there a clear Revenue Analytics case definition?
<--- Score
105. Is there a completed SIPOC representation, describing the Suppliers, Inputs, Process, Outputs, and Customers?
<--- Score
106. The political context: who holds power?
<--- Score
107. What defines best in class?
<--- Score
108. Are task requirements clearly defined?
<--- Score
109. Are roles and responsibilities formally defined?
<--- Score
110. 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
111. Does the team have regular meetings?
<--- Score
112. What key stakeholder process output measure(s) does Revenue Analytics leverage and how?
<--- Score
113. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?
<--- Score
114. What system do you use for gathering Revenue Analytics information?
<--- Score
115. How do you gather Revenue Analytics requirements?
<--- Score
116. What sources do you use to gather information for a Revenue Analytics study?
<--- Score
117. Is there any additional Revenue Analytics definition of success?
<--- Score
118. What specifically is the problem? Where does it occur? When does it occur? What is its extent?
<--- Score
119. What happens if Revenue Analytics’s scope changes?
<--- Score
120. 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
121. Has the direction changed at all during the course of Revenue Analytics? If so, when did it change and why?
<--- Score
122. How do you catch Revenue Analytics definition inconsistencies?
<--- Score
123. Has a project plan, Gantt chart, or similar been developed/completed?
<--- Score
124. What is the worst case scenario?
<--- Score
125. What is the context?
<---