Decision Log: Software AG223
3.5 Quality Audit: Software AG225
3.6 Team Directory: Software AG228
3.7 Team Operating Agreement: Software AG230
3.8 Team Performance Assessment: Software AG232
3.9 Team Member Performance Assessment: Software AG234
3.10 Issue Log: Software AG236
4.0 Monitoring and Controlling Process Group: Software AG238
4.1 Project Performance Report: Software AG240
4.2 Variance Analysis: Software AG242
4.3 Earned Value Status: Software AG244
4.4 Risk Audit: Software AG246
4.5 Contractor Status Report: Software AG248
4.6 Formal Acceptance: Software AG250
5.0 Closing Process Group: Software AG252
5.1 Procurement Audit: Software AG254
5.2 Contract Close-Out: Software AG256
5.3 Project or Phase Close-Out: Software AG258
5.4 Lessons Learned: Software AG260
Index262
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. How do you identify subcontractor relationships?
<--- Score
2. Looking at each person individually – does every one have the qualities which are needed to work in this group?
<--- Score
3. Who should resolve the Software AG issues?
<--- Score
4. Are there Software AG problems defined?
<--- Score
5. What else needs to be measured?
<--- Score
6. Which needs are not included or involved?
<--- Score
7. How are the Software AG’s objectives aligned to the group’s overall stakeholder strategy?
<--- Score
8. Did you miss any major Software AG issues?
<--- Score
9. Is it needed?
<--- Score
10. Can management personnel recognize the monetary benefit of Software AG?
<--- Score
11. Do you need different information or graphics?
<--- Score
12. What are the stakeholder objectives to be achieved with Software AG?
<--- Score
13. What needs to stay?
<--- Score
14. Are you dealing with any of the same issues today as yesterday? What can you do about this?
<--- Score
15. For your Software AG project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
16. What needs to be done?
<--- Score
17. Why is this needed?
<--- Score
18. What problems are you facing and how do you consider Software AG will circumvent those obstacles?
<--- Score
19. Are there any revenue recognition issues?
<--- Score
20. How does it fit into your organizational needs and tasks?
<--- Score
21. Will Software AG deliverables need to be tested and, if so, by whom?
<--- Score
22. Who needs budgets?
<--- Score
23. Whom do you really need or want to serve?
<--- Score
24. Who are your key stakeholders who need to sign off?
<--- Score
25. How do you recognize an objection?
<--- Score
26. What is the extent or complexity of the Software AG problem?
<--- Score
27. Where is training needed?
<--- Score
28. What vendors make products that address the Software AG needs?
<--- Score
29. How are training requirements identified?
<--- Score
30. Consider your own Software AG project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
31. How are you going to measure success?
<--- Score
32. Think about the people you identified for your Software AG project and the project responsibilities you would assign to them, what kind of training do you think they would need to perform these responsibilities effectively?
