Using the guidelines in the attached document, write a project audit report. Be sure to include project classification, analysis of information gathered, recommendations, and lessons learned. You may also include an appendix of appropriate documentation.

There is a handwritten note on the docment. Please follow that handwritten directions on the pdf. i.e. Please complete the questions in sections 2, 3, 4, and 5 to complete the project audit.

Project Bugdet- $270,000

We have 5 periods- Period 0- (Pre-Play Period)- $270,000, Period 1- (Play Period)- Period costs- $26,548, Balance- $243,452; Period 2- (Play Period)- Period costs- $60,974, Balance- $182,478; Period 3- (Play Period)- Period costs- $77,911, Balance- $104,567

2. Analysis. The analysis section includes succinct, factual review statements of the project (PMBOK, 2017)-for example, . Scope objectives, the criteria used to evaluate scope and evidence that the comple- tion criteria were met. . Quality objectives, the criteria used to assess the project and product/service qual- ity, and reasons for variances. . Cost objectives, including acceptable cost range, actual costs, and reasons for any variances. . Schedule objectives, including verification of milestone completion dates, and rea- sons for variances. Summary of risks and issues encountered on the project and how they were addressed. . Outcomes achieved, including an assessment of how the final product, service, or result addressed the business need identified in the selection process. 3. Recommendations. Usually audit recommendations represent major corrective actions that should take place. Audit recommendations are often technical and focus on solutions to problems that surfaced. For example, to avoid rework, the report of a construction project recommended shifting to a more resilient building material. In other cases, recommendations may include terminating or sustaining vendor or con- tractor relationships. 4. Lessons learned. These do not have to be in the form of recommendations. Lessons learned serve as reminders of mistakes easily avoided and actions easily taken to ensure success. In practice, new project teams reviewing audits of past proj- ects similar to the one they are about to start have found audit reports very useful. Team members will frequently remark later, "The recommendations were good, but the 'lessons learned' section really helped us avoid many pitfalls and made our project implementation smoother." It is precisely for this reason that lessons learned in the form of project retrospectives have taken on greater prominence and warrant further discussion. See Snapshot from Practice 14.3: Operation Eagle Claw. 5. Appendix. The appendix may include backup data or details of analysis that allow others to follow up if they wish. It should not be a dumping ground used for filler; only critical, pertinent information should be attached