61. Are there any constraints known that bear on the ability to perform Revenue Analytics work? How is the team addressing them?
<--- Score
62. What is out of scope?
<--- Score
63. Is there a critical path to deliver Revenue Analytics results?
<--- Score
64. If substitutes have been appointed, have they been briefed on the Revenue Analytics goals and received regular communications as to the progress to date?
<--- Score
65. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
66. How can the value of Revenue Analytics be defined?
<--- Score
67. Is Revenue Analytics required?
<--- Score
68. Where can you gather more information?
<--- Score
69. How will variation in the actual durations of each activity be dealt with to ensure that the expected Revenue Analytics results are met?
<--- Score
70. What gets examined?
<--- 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?
<---
