Score
15. Scope of sensitive information?
<--- Score
16. Does the scope remain the same?
<--- Score
17. What are the Revenue Analytics tasks and definitions?
<--- Score
18. Is it clearly defined in and to your organization what you do?
<--- Score
19. What is the definition of Revenue Analytics excellence?
<--- Score
20. What is the scope of the Revenue Analytics effort?
<--- Score
21. What constraints exist that might impact the team?
<--- Score
22. What is the scope of the Revenue Analytics work?
<--- Score
23. What are the Revenue Analytics use cases?
<--- Score
24. Who defines (or who defined) the rules and roles?
<--- Score
25. What was the context?
<--- Score
26. Who approved the Revenue Analytics scope?
<--- Score
27. What is in the scope and what is not in scope?
<--- Score
28. Do you all define Revenue Analytics in the same way?
<--- Score
29. Why are you doing Revenue Analytics and what is the scope?
<--- Score
30. Has a team charter been developed and communicated?
<--- Score
31. What is in scope?
<--- Score
32. Are there different segments of customers?
<--- Score
33. Is the current ‘as is’ process being followed? If not, what are the discrepancies?
<--- Score
34. How are consistent Revenue Analytics definitions important?
<--- Score
35. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
36. How do you gather the stories?
<--- Score
37. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
38. How do you think the partners involved in Revenue Analytics would have defined success?
<--- Score
39. Is there regularly 100% attendance at the team meetings? If not, have appointed substitutes attended to preserve cross-functionality and full representation?
<--- Score
40. How have you defined all Revenue Analytics requirements first?
<--- Score
41. What are the record-keeping requirements of Revenue Analytics activities?
<--- Score
42. How do you build the right business case?
<--- Score
43. What is out-of-scope initially?
<--- Score
44. What sort of initial information to gather?
<--- Score
45. When is the estimated completion date?
<--- Score
46. Has a Revenue Analytics requirement not been met?
<--- Score
47. How is the team tracking and documenting its work?
<--- Score
48. What information should you gather?
<--- Score
49. How does the Revenue Analytics manager ensure against scope creep?
<--- Score
50. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
51. Is the Revenue Analytics scope manageable?
<--- Score
52. How often are the team meetings?
<--- Score
53. Is the work to date meeting requirements?
<--- Score
54. Is the scope of Revenue Analytics defined?
<--- Score
55. What would be the goal or target for a Revenue Analytics’s improvement team?
<--- Score
56. Are the Revenue Analytics requirements testable?
<--- Score
57. What are the core elements of the Revenue Analytics business case?
<--- Score
58. How would you define the culture at your organization, how susceptible is it to Revenue Analytics changes?
<--- Score
59. What intelligence can you gather?
<--- Score
60. What knowledge or experience is required?
<---
