Probability and Impact Matrix: Construction Estimating Software206
2.35 Risk Data Sheet: Construction Estimating Software208
2.36 Procurement Management Plan: Construction Estimating Software210
2.37 Source Selection Criteria: Construction Estimating Software212
2.38 Stakeholder Management Plan: Construction Estimating Software214
2.39 Change Management Plan: Construction Estimating Software216
3.0 Executing Process Group: Construction Estimating Software218
3.1 Team Member Status Report: Construction Estimating Software220
3.2 Change Request: Construction Estimating Software222
3.3 Change Log: Construction Estimating Software224
3.4 Decision Log: Construction Estimating Software226
3.5 Quality Audit: Construction Estimating Software228
3.6 Team Directory: Construction Estimating Software231
3.7 Team Operating Agreement: Construction Estimating Software233
3.8 Team Performance Assessment: Construction Estimating Software235
3.9 Team Member Performance Assessment: Construction Estimating Software237
3.10 Issue Log: Construction Estimating Software239
4.0 Monitoring and Controlling Process Group: Construction Estimating Software241
4.1 Project Performance Report: Construction Estimating Software243
4.2 Variance Analysis: Construction Estimating Software245
4.3 Earned Value Status: Construction Estimating Software247
4.4 Risk Audit: Construction Estimating Software249
4.5 Contractor Status Report: Construction Estimating Software251
4.6 Formal Acceptance: Construction Estimating Software253
5.0 Closing Process Group: Construction Estimating Software255
5.1 Procurement Audit: Construction Estimating Software257
5.2 Contract Close-Out: Construction Estimating Software259
5.3 Project or Phase Close-Out: Construction Estimating Software261
5.4 Lessons Learned: Construction Estimating Software263
Index265
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 the kinds of information that you will need?
<--- Score
2. Who are your key stakeholders who need to sign off?
<--- Score
3. Is the quality assurance team identified?
<--- Score
4. Is the need for organizational change recognized?
<--- Score
5. Where is training needed?
<--- Score
6. Which issues are too important to ignore?
<--- Score
7. What does Construction Estimating Software success mean to the stakeholders?
<--- Score
8. What is the smallest subset of the problem you can usefully solve?
<--- Score
9. Are employees recognized for desired behaviors?
<--- Score
10. What is the recognized need?
<--- Score
11. What creative shifts do you need to take?
<--- Score
12. How do you recognize an objection?
<--- Score
13. Are your goals realistic? Do you need to redefine your problem? Perhaps the problem has changed or maybe you have reached your goal and need to set a new one?
<--- Score
14. What extra resources will you need?
<--- Score
15. Are there any specific expectations or concerns about the Construction Estimating Software team, Construction Estimating Software itself?
<--- Score
16. Can management personnel recognize the monetary benefit of Construction Estimating Software?
<--- Score
17. What are the timeframes required to resolve each of the issues/problems?
<--- Score
18. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
19. What activities does the governance board need to consider?
<--- Score
20. Which information does the Construction Estimating Software business case need to include?
<--- Score
21. Do you need to avoid or amend any Construction Estimating Software activities?
<--- Score
22. Consider your own Construction Estimating 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
23. What is the problem and/or vulnerability?
<---
