Kay is the project manager of the QUI Project. This project is done but is also considerably over
budget. Kay has elected to crash the project
in order to recoup schedule delays but this increased the project costs. What should Kay do with the
information regarding the schedule
delays and cost overruns?
When there have been significant corrective action decisions the reasoning behind the
decision should be documented in the lessons learned
documentation.
What is lessons learned documentation?
Lessons learned documentation is prepared to contribute to the lessons learned knowledge
database of the organization.
It includes the causes of issues, the reasoning behind the corrective action chosen, and other types
of lessons learned
about stakeholder management. Lessons learned are documented so that they become part of the
historical database for
the project/program and the performing organization. The lessons learned are compiled, formalized,
and stored through
out the project's/program's duration.
Answer option C is incorrect. A variance report may be appropriate but cost and schedule variances
are reported differently. Kay could create
a cost variance report and a schedule variance report, but not one report for both project attributes.
Answer option B is incorrect. An exceptions report is the same as a variance report. Kay would
create a separate exceptions report for cost,
and another for schedule.
Answer option D is incorrect. The information may go into the project final report but it should be
included in the project's lessons learned
information when it is discovered.
Currently there are no comments in this discussion, be the first to comment!