A project manager is organizing and running a project closure meeting. Which of the following best describes the objective of this meeting?
Correct Answer:
B
A project closure meeting is a formal gathering held at the end of a project timeline. Its chief purpose is to evaluate the project’s performance, identify and discuss the achieved outcomes, successes, and challenges, and confirm that all predefined tasks and objectives have been completed successfully1. The project closure meeting also involves obtaining project sign-off from all necessary parties, such as the project sponsor, the client, the stakeholders, and the team members. Project sign-off is the official approval that the project has met the agreed-upon criteria and quality standards, and that the project is formally closed2.
During the execution phase, user accepted testing failed; nonetheless, the vendor PM is insisting that the program manager approve the invoice for this phase. Which of the following actions should the Program manager take?
Correct Answer:
D
The program manager should schedule a call with the vendor PM and vendor executive to review the statement of work (SOW), which is a document that defines the scope, deliverables, timeline, quality, and payment terms of the project. The program manager should clarify the expectations and criteria for user acceptance testing (UAT), which is a process of verifying that the system meets the user’s requirements and expectations. The program manager should also discuss the reasons for the UAT failure
and the corrective actions needed to resolve the issues. The program manager should not approve the invoice until the UAT is successfully completed, as this would compromise the quality and value of the project. The program manager should also not escalate the issue or work on a compromise without first reviewing the SOW and communicating with the vendor12.
A stakeholder works in a remote location and has not been replying to emails. The Internet service in that location is intermittent, and the stakeholder prefers to be contacted by telephone. Which of the following artifacts should the project manager have prepared to avoid this situation?
Correct Answer:
B
The project manager should have prepared acceptable communication channels to avoid the situation of a stakeholder not replying to emails due to intermittent Internet service. Acceptable communication channels are methods or modes of communication that are agreed upon by all parties involved in a project. They may include aspects such as email, phone call, text message, video conference, instant message, or face-to-face meeting. Acceptable communication channels can help to ensure that messages are delivered and received effectively and efficiently and that communication preferences and limitations are respected.
SIMULATION
During a gate review meeting, the deliverable was rejected by the customer. INSTRUCTIONS
Review the dashboard.
• Part 1: Drag and drop each task, placing them in the correct order based on the project change control process.
• Part 2: Select the proper document(s) to be updated.
If at any time you would like to bring back the initial state of the simulation, please click the Reset All button.
Part 1:
Part 2:
Solution:
Part 1:
Change Control Process:
✑ Consult the RACI matrix.
✑ Define new requirements and record changes.
✑ Assess the schedule, risk, and cost.
✑ Perform a demonstration.
✑ Obtain a sign off.
✑ Update and test the deliverable.
✑ Make an announcement on the company portal.
The change control process is a sequence of steps that helps to manage and document any changes or modifications to a project scope, schedule, cost, quality, or resources. The change control process typically involves the following steps:
✑ Consult the RACI matrix. A RACI matrix is a tool that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project.
RACI stands for responsible, accountable, consulted, and informed. Consulting the RACI matrix can help to identify who needs to be involved or informed about the change request and how to communicate with them.
✑ Define new requirements and record changes. The new requirements and changes are the details of what needs to be modified or added to the project deliverables or objectives based on the customer feedback or request. Defining and recording the new requirements and changes can help to communicate and justify the need and rationale for the change and its implications on the project scope and quality.
✑ Assess the schedule, risk, and cost. The schedule, risk, and cost are the aspects of the project that may be affected by the change request. Assessing the schedule, risk, and cost can help to determine the impact and feasibility of the change and identify any possible alternatives or corrective actions to minimize or avoid its negative effects.
✑ Perform a demonstration. A demonstration is a presentation or show of how the modified or updated deliverable works or meets the customer expectations or requirements. Performing a demonstration can help to validate and verify that the change request has been implemented correctly and effectively and to obtain feedback or approval from the customer or stakeholders.
✑ Obtain a sign off. A sign off is a formal acceptance and approval of the change request and its deliverables from the customer or stakeholders. Obtaining a sign off can help to confirm that the change request has been completed successfully and satisfactorily and to close the change control process.
✑ Update and test the deliverable. The deliverable is the product or service that is produced or provided by the project. Updating and testing the deliverable can help to ensure that it meets the quality standards and criteria and that it works as expected after implementing the change request.
✑ Make an announcement on the company portal. The company portal is a platform or channel that allows internal communication and collaboration among employees within an organization. Making an announcement on the company portal can help to inform and update other team members or departments about the change request and its outcomes and to share any lessons learned or best practices from the change control process.
Part2:
✑ Risk register: A risk register is a document that identifies, analyzes, and records the potential risks or uncertainties that may affect a project. Updating the risk register can help to capture any new or modified risks that may arise from the change request and to plan and implement appropriate risk responses.
✑ Schedule: A schedule is a document that shows the planned start and end dates,
durations, dependencies, and progress of each task or activity in a project. Updating the schedule can help to reflect any changes or adjustments to the project timeline or milestones that may result from the change request and to monitor and control the project performance and delivery.
✑ Statement of work: A statement of work (SOW) is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. Updating the SOW can help to document any changes or additions to the project scope or deliverables that may be requested or agreed upon by the customer or stakeholders and to ensure alignment and agreement on what needs to be done and how it will be done.
✑ Change log: A change log is a document that tracks and records any changes or modifications that are made to the project scope, schedule, cost, quality, or resources during a project. Updating the change log can help to document the change request, approval, implementation, and impact of each change and ensure traceability and transparency.
Does this meet the goal?
Correct Answer:
A
A new junior PM who has ownership of a project does not understand how to manage conflicts involving multiple personalities. Which of the following is the best order of the stages the PM should follow to nurture the team to high performance?
Correct Answer:
D
This is the correct order of the stages of team development according to Tuckman’s model123. The forming stage is where team members first meet and get acquainted. The storming stage is where team members experience conflicts and disagreements. The norming stage is where team members resolve their differences and establish norms and rules. The performing stage is where team members work together effectively and efficiently. The adjourning stage is where team members complete the project and celebrate their achievements. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Project Team Management, p. 197; The 5 Stages of Team Development (Including Examples) | Upwork; The 5 Stages of Team Development
- Teamwork; Using the Stages of Team Development | MIT Human Resources
