Team Member Status Report: Revenue Analytics215
3.2 Change Request: Revenue Analytics217
3.3 Change Log: Revenue Analytics219
3.4 Decision Log: Revenue Analytics221
3.5 Quality Audit: Revenue Analytics223
3.6 Team Directory: Revenue Analytics226
3.7 Team Operating Agreement: Revenue Analytics228
3.8 Team Performance Assessment: Revenue Analytics230
3.9 Team Member Performance Assessment: Revenue Analytics232
3.10 Issue Log: Revenue Analytics234
4.0 Monitoring and Controlling Process Group: Revenue Analytics236
4.1 Project Performance Report: Revenue Analytics238
4.2 Variance Analysis: Revenue Analytics240
4.3 Earned Value Status: Revenue Analytics242
4.4 Risk Audit: Revenue Analytics244
4.5 Contractor Status Report: Revenue Analytics246
4.6 Formal Acceptance: Revenue Analytics248
5.0 Closing Process Group: Revenue Analytics250
5.1 Procurement Audit: Revenue Analytics252
5.2 Contract Close-Out: Revenue Analytics254
5.3 Project or Phase Close-Out: Revenue Analytics256
5.4 Lessons Learned: Revenue Analytics258
Index260
CRITERION #1: RECOGNIZE
INTENT: Be aware of the need for change. Recognize that there is an unfavorable variation, problem or symptom.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Are problem definition and motivation clearly presented?
<--- Score
2. Who needs to know about Revenue Analytics?
<--- Score
3. How do you assess your Revenue Analytics workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
4. What do you need to start doing?
<--- Score
5. Is the need for organizational change recognized?
<--- Score
6. How do you identify subcontractor relationships?
<--- Score
7. Which needs are not included or involved?
<--- Score
8. How do you recognize an Revenue Analytics objection?
<--- Score
9. How can auditing be a preventative security measure?
<--- Score
10. When a Revenue Analytics manager recognizes a problem, what options are available?
<--- Score
11. What is the problem and/or vulnerability?
<--- Score
12. How do you identify the kinds of information that you will need?
<--- Score
13. What Revenue Analytics coordination do you need?
<--- Score
14. Does your organization need more Revenue Analytics education?
<--- Score
15. What tools and technologies are needed for a custom Revenue Analytics project?
<--- Score
16. What Revenue Analytics capabilities do you need?
<--- Score
17. Who are your key stakeholders who need to sign off?
<--- Score
18. Did you miss any major Revenue Analytics issues?
<--- Score
19. Is it needed?
<--- Score
20. How are you going to measure success?
<--- Score
21. Why is this needed?
<--- Score
22. Whom do you really need or want to serve?
<--- Score
23. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
24. What training and capacity building actions are needed to implement proposed reforms?
<--- Score
25. Will new equipment/products be required to facilitate Revenue Analytics delivery, for example is new software needed?
<--- Score
26. What are the Revenue Analytics resources needed?
<--- Score
27. Have you identified your Revenue Analytics key performance indicators?
<--- Score
28. Will Revenue Analytics deliverables need to be tested and, if so, by whom?
<--- Score
29. Does the problem have ethical dimensions?
<--- Score
30. What is the smallest subset of the problem you can usefully solve?
<---
