Source Selection Criteria: Decision Support Software211
2.38 Stakeholder Management Plan: Decision Support Software213
2.39 Change Management Plan: Decision Support Software215
3.0 Executing Process Group: Decision Support Software217
3.1 Team Member Status Report: Decision Support Software219
3.2 Change Request: Decision Support Software221
3.3 Change Log: Decision Support Software223
3.4 Decision Log: Decision Support Software225
3.5 Quality Audit: Decision Support Software227
3.6 Team Directory: Decision Support Software229
3.7 Team Operating Agreement: Decision Support Software231
3.8 Team Performance Assessment: Decision Support Software233
3.9 Team Member Performance Assessment: Decision Support Software235
3.10 Issue Log: Decision Support Software237
4.0 Monitoring and Controlling Process Group: Decision Support Software239
4.1 Project Performance Report: Decision Support Software241
4.2 Variance Analysis: Decision Support Software243
4.3 Earned Value Status: Decision Support Software245
4.4 Risk Audit: Decision Support Software247
4.5 Contractor Status Report: Decision Support Software249
4.6 Formal Acceptance: Decision Support Software251
5.0 Closing Process Group: Decision Support Software253
5.1 Procurement Audit: Decision Support Software255
5.2 Contract Close-Out: Decision Support Software257
5.3 Project or Phase Close-Out: Decision Support Software259
5.4 Lessons Learned: Decision Support Software261
Index263
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. Who are your key stakeholders who need to sign off?
<--- Score
2. What are the Decision support software resources needed?
<--- Score
3. What tools and technologies are needed for a custom Decision support software project?
<--- Score
4. Are there any specific expectations or concerns about the Decision support software team, Decision support software itself?
<--- Score
5. What are your needs in relation to Decision support software skills, labor, equipment, and markets?
<--- Score
6. What is the Decision support software problem definition? What do you need to resolve?
<--- Score
7. Will Decision support software deliverables need to be tested and, if so, by whom?
<--- Score
8. How are you going to measure success?
<--- Score
9. What should be considered when identifying available resources, constraints, and deadlines?
<--- Score
10. What vendors make products that address the Decision support software needs?
<--- Score
11. What would happen if Decision support software weren’t done?
<--- Score
12. Why is this needed?
<--- Score
13. Can management personnel recognize the monetary benefit of Decision support software?
<--- Score
14. Do you know what you need to know about Decision support software?
<--- Score
15. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
16. Consider your own Decision support software project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
17. How many trainings, in total, are needed?
<--- Score
18. How can auditing be a preventative security measure?
<--- Score
19. Are there regulatory / compliance issues?
<--- Score
20. For your Decision support software project, identify and describe the business environment, is there more than one layer to the business environment?
<--- Score
21. Are there recognized Decision support software problems?
<--- Score
22. Did you miss any major Decision support software issues?
<--- Score
23. Is the quality assurance team identified?
<--- Score
24. How do you identify the kinds of information that you will need?
<--- Score
25. What is the recognized need?
<---
