During a project, a business need changes and the project is cancelled. The project manager meets with project team members to collect information learned during the project.
Where this information should be documented?


A. Issue log
B. Organizational process assets
C. Enterprise environmental factors
D. Status report

A project team completed all development activities and delivered the product to the customer. The project manager immediately released the team to begin work on a new product. One month later, the customer complains that many functionalities fail to work as
expected.

What should the project manager have done to avoid this?


A. Updated the organizational process assets.
B. Ensured that formal approval was obtained from the customer
C. Revised the requirements traceability matrix
D. Transferred the project to the maintenance and support team

A project is completed, and the product design packaging is delivered and accepted by the customers design engineer. However, customer payment is still unresolved due to a concern about the products warranty.
What should the project manager do next?


A. Review the contract to ensure that all project requirements are complete.
B. Document historical information and lessons learned.
C. Coordinate payment issues with the customer.
D. Review the customer acceptance document.

An increase in the number of client-requested deliverables has been addressed by updating the acceptance test criteria. These new deliverables, along with increased quality testing, result in a delay in achieving project milestones.
What should the project manager do?


A. Submit a change request to the change control board (CCB).
B. Revise the quality management plan.
C. Request additional resources to meet the updated acceptance test criteria.
D. Complete the project according to the original acceptance test criteria.

During a project review meeting, stakeholders disagree on the project deliverables outlined in the acceptance criteria. According to one stakeholder, the project fails to deliver what they understood the acceptance criteria stated it would deliver.
What should the project manager have done to ensure that all project stakeholders understood the acceptance criteria?


A. Evaluated the project management plan with all stakeholders
B. Met with all stakeholders and team members to update the project management plan.
C. Reviewed project deliverables with all stakeholders
D. Conducted a stakeholder workshop to define and agree on measurable project deliverables.

A project manager is validating a projects scope. Although the customer agrees that the final product meets the scope described in the project management plan, they have rejected the product due to perceived quality deficiencies.
What should the project manager do next?


A. Explain to the customer that it is a requirement to follow the scope plan.

B. Perform a quality audit to compare final performance against the original performance requirements.
C. Process a change request to tailor the quality management plan to the final product performance results.
D. Maintain the final product performance as is, update the lessons learned repository, and move to the formal project close-out stage.

A software development project is approaching the close-out phase. The team is completing development and testing of the new system, and the project manager is preparing documents for the final project meetings.
What meeting should the project manager conduct next?


A. Lessons learned
B. Service transition
C. Benefits analysis
D. Scope validation

A project manager is determining the accuracy of the deliverables before closing a project. What process should be used to determine this and is an input to formalizing acceptance?


A. Control Scope
B. Manage Quality
C. Plan Scope Management
D. Control Quality

A project is delivered that meets the approved business requirements. However, the client identifies a few unrelated issues that will cause a delay in final product approval and impact project closure.
What should the project manager do?


A. Discuss the impact with the client, obtain acceptance, and formally close the project.
B. Follow the escalation process, develop the hand-over report, and formally close the project.
C. Document the unrelated issues, develop the hand-over report, and formally close the project.
D. Resolve the unrelated issues, obtain acceptance, and formally close the project.

At the final project closeout meeting, the customer informs the project manager that they require only selected parts of the project information. What should the project manager do with the documentation internally?


A. Comply with the current legislation for document retention.
B. Archive project documents per their own companys document retention policies.

C. Remove the unnecessary parts of the documentation to match the customers request.
D. Archive the entire documentation in the project management office (PMO) for retrieval upon customer request.