PMI PMP - Project Management Professional (2025 Version)

Demonstrate that risky projects are subject to change so adding reserves to the budget is a necessity.

Explain to the project sponsor and key stakeholders the need to add the reserve and get their buy-in.

Seek key stakeholders' approval and finalize the budget with the reserve.

Agree with the project sponsor and finalize the budget without the reserve.

Go back to the customer and explain that they cannot implement the feature completely in one iteration.

Reduce the scope of the feature to fit into one iteration and deliver it to the customer

Ask the customer to simplify the feature so that it can be implemented in one iteration

Split the feature into smaller subfeatures. implement them, and then deliver them incrementally in multiple iterations

Create incentives to promote better communication among team members.

Assign the work packages based on geographical working groups.

Understand and consider the emotions of each team member.

Plan for communication training workshops for all team members.

Review the work packages, schedule, and estimates with the team and consolidate tasks to shorten the schedule.

Schedule more frequent design reviews with the customers and provide prototypes to demonstrate progress and gather feedback.

Ask the sponsor for additional resources and funding to speed up the work and cover additional labor costs.

Review work packages with the team to build a new incremental delivery plan with multiple releases and obtain the customers' feedback.

Recommend a change in the project methodology or the approach.

Develop and execute a stakeholder engagement strategy.

Determine the criteria and measuring systems for objective success.

Allocate more time for mentoring project team members.

Develop the project management plan based on the requirements requested by the customer.

Develop the application as requested by the customer, based on the approved project requirements.

Plan a minimum viable product (MVP) to get early feedback from the customer.

Facilitate a focus group to assess the functionality before development.

Use an agile approach to deliver the product based on sprints.

Involve team members in stakeholder analysis and engagement.

Invite all stakeholders to progress meetings to avoid ambiguity.

Ensure team members have access to a well-written requirements traceability matrix.

Engage with the project sponsor and ensure the product backlog is correct and up to date.

Negotiate with the product owner to determine which functionality should be pushed out of the scope of the project.

Discuss with the team how this change in scope impacts development at the next retrospective to determine next steps.

Negotiate with the product owner to determine what might be removed from the backlog that is of similar size.

Add the functionality to the product backlog for inclusion once a change request is created and approved.

Communicate the risks and propose hiring members with leadership experience before continuing with the request.

Decline the scope expansion until the team members get appropriate leadership opportunities within the project.

Implement the scope expansion and suggest the team members get a mentor due to their lack of leadership experience.

Recognize each team member for their contributions and recommend them to the leadership development program.

Assign a resource from the core team to handle the acquisition.

Register a risk and escalate it to the project sponsor.

Update the status report with information about this dependency.

Register a risk and monitor its exposure variation.

Inform the sponsor that the team is unable to complete the requests due to a lack of funding, and defer the project.

Prioritize the scope items to determine the duration needed for a minimal viable product (MVP) and adjust the funding request.

Have the team work on the list of requests from the sponsor without modification until the 6-month period ends.

Request the team complete all scope items, with the assumption of securing additional funding within 6 months.

Send the team to a data center optimization training workshop.

Partner with a company that is an expert in this area.

Outsource the data center optimization work to a vendor.

Request a budget to build this competency among project team members.

Speak with the vendor and explain that constant updates are impacting the project and request an action plan to minimize the changes.

Schedule a spike meeting, conduct risk assessments, and incorporate them into the backlog to help with risk mitigation.

Explain to the project team that the vendor's updates are something unpredictable, and the team must continue working on the project.

Schedule a retrospective meeting and conduct a risk assessment with the team, implementing mitigation tasks before the next sprint.

Escalating a conflict within the project

Creating a new communication channel

Giving special attention to this stakeholder

Dismissing the stakeholder's opinions

Schedule a meeting with the project sponsor to report and discuss the issue.

Update the project schedule in response to the external crisis.

Develop a contingency plan and seek alternative suppliers.

Assess and consolidate projects phases and update the project management plan.

Apply the critical path method (CPM).

Use the Delphi Technique.

Use the Monte Carlo analysis online.

Utilize story point estimating.

Leverage the project governance system to track and manage the project artifacts.

Create a central repository system to assess the effectiveness of the project artifacts.

Review the execution roadmap and ask the legal team to manage the artifacts.

Ensure the project artifacts are kept up to date and accessible to all stakeholders.

Work with the team to determine the process to manage the project artifacts.

This framework is not appropriate for agile.

This is a learning experience for the agile team.

An agile approach is easily adaptable.

An agile approach is different.

Ask the project sponsor to help with engagement of the key stakeholders.

Communicate project outcomes and results with the key stakeholders.

Define a high-level project scope and share it with the key stakeholders.

Conduct a workshop on project goals and deliverables with the key stakeholders.

Arrange a group meeting with the stakeholders to generate creative alternatives.

Address the conflict in a planned meeting with all stakeholders and project team members.

Assess the conflict based upon the stakeholders' past disagreements.

Focus on the personal issues between the stakeholders.

Create a messaging group chat with the branch office stakeholders to inform them about the project delay.

Schedule a video conference to inform the branch office stakeholders about the project delay.

Send an official project memo to inform the branch office stakeholders about the project delay.

Include the project delay in the monthly progress report for the branch office stakeholders.

Involve all of the stakeholders in the escalation by setting up a conference call.

Escalate to the other party's management and inform the steering committee.

Reach out to peer managers for similar escalation situations and follow past experiences.

Review the established project escalation process and take the appropriate action.

Assess the benefit of using new technology versus old technology.

Hire project resources with experience using the new technology.

Propose training for the project team in batches on the new technology.

Request incentives for the team to use the new technology.

Identified the stakeholders and their expectations

Presented the project to the community

Added this situation to the risk register

Added these requests to the project scope statement

Obtain approval from sponsors to increase the rates because it can affect project due to lack of resources.

Carefully read the agreements and see if there was any clause if the per hour rate could be increased.

Assign a team member to negotiate the increased wage per hour with the labor union representatives.

Negotiate with the labor union representatives if the clause about increased wage per hour meets their requirements.

Meet each team member during their work hours to ensure all questions are answered in a timely manner.

Inform all team members that they are required to check for messages every few hours to ensure fast response times.

During daily check-ins, compile questions, coordinate with all team members, and agree to meet.

Escalate to the project sponsor and request to replace certain team members so the time zones are aligned.

Ask the developers to use peer programming.

Build a task board on a large wall using sticky notes.

Build a detailed schedule and describe each task in detail.

Ask the product owner to reprioritize the backlog.

High accountability, little authority

Available resources, bad roadmaps

Good roadmaps, little accountability

Enough authority, insufficient resources

Align the project goals with the team member.

Reassign the team member to another project.

Nominate the team member to receive agile training.

Allocate another resource to support the team member.

The project was completed behind schedule.

The requirements gathering was inadequate.

The risk analysis was inadequate.

The project was delivered above budget.

Hold separate retrospective meetings for both the vendor team and the internal team.

Schedule a preliminary meeting with the account manager from the vendor and the test manager.

Establish a clear agenda for the meeting and remind the vendor and internal teams that the scope is to improve the process.

Invite the procurement manager and a representative from the vendor to manage the current tense relationship.

Communicate to the stakeholders that the project has to be delayed for two weeks.

Ask the project team to accept the shorter estimate as it is important to keep a good relationship with the product owner.

Decide what should be the time estimate and proceed with the planning meeting.

Educate the product owner that the project team members are the most appropriate group for assessing the effort.

Summarize the project report so it can be more efficient to read and send it to the project sponsor.

Ensure the communications methods, channels, frequency, and level of detail for the stakeholders are what is needed.

Reinforce the need to document and provide updated information to make the process transparent.

Include a task in every iteration to allocate time for the project team to complete the documentation updates.

Sprint review meeting

Retrospective meeting

Daily Scrum meeting

Sprint planning meeting

Add the issue to the issue log and communicate the issue in the next regular report to project stakeholders.

Escalate the issue to the project sponsor notifying them of the slow services from the department.

Send all service requests to the department earlier in the project to lessen the impact on the delivery date.

Arrange a meeting with the leader to explain the project's needs and understand the leader's perspective.

Review the risk impact of quality nonconformance.

Review the communications management plan.

Revise the quality management plan.

Revise the product acceptance specifications.

Set up regular project status meetings and invite all team members.

Encourage the team to define the ground rules for performance.

Set up individual calls to follow up on each team member's progress.

Invite team members to an informal meeting to get to know one another.

Perform contract, financial, and administrative tasks.

Finalize the in-progress administrative tasks.

Evaluate contract and administrative tasks.

Execute financial and administrative tasks.

Share a presentation with information about each project team member.

Share all members' resumes and photographs in a sharing digital platform.

Schedule multiple one-on-one meetings between team members.

Schedule a kickoff meeting to present the whole project team.

Develop a communications management plan that reflects the needs of the stakeholder community.

Engage with each stakeholder to determine their information needs related to the project.

Create a responsible, accountable, consulted, and informed (RACI) chart based on the stakeholders and their communications needs.

Determine the most appropriate mechanisms to leverage when communications are necessary.

Allocate additional resources to the development team to ensure the original scope can be completed on time.

Suggest prioritizing the most critical features for the next sprint as well as reevaluating the remaining scope.

Agree on reducing the scope to match the team's resources and plan to add the removed items to future sprints.

Insist on keeping the original scope and explain the importance of meeting all the project milestones on time.

Escalate to the project sponsor to provide a solution to the conflict.

Interpret the source and stage of the conflict and select a resolution approach.

Apply a compromising resolution approach, involving both groups.

Ask the functional managers of both groups to help find a workable solution.

Project team

Project management office (PMO)

Quality lead

Product owner

Register the issue as a risk with the project team members.

Review the project schedule with project team members and the suppliers.

Advise the procurement department to develop a new supplier strategy.

Use the procurement and risk management plans to manage this issue.

Asked the project sponsor to review the budget

Updated the budget before moving to another stage of the project

Added enough budget to cover all uncertainties

Used past projects as a reference during budget estimations

Review the information radiators for each project.

Connect with each project's scrum master to assess progress.

Meet with each project's development team separately.

Attend the daily standup meetings for each project.

Evaluate the schedule performance index (SPI) trend for slack to enable all five sprints while maintaining the cost performance index (CPI).

Instruct the scrum master to suspend the current sprints and initiate the critical sprints immediately.

Ask the scrum master to identify why sprints are in process for work that is not on the critical path.

Contact the project sponsor to request adjustment to the completion date and to enable the current workflow.

Ask the team member to contact the learning and development team for additional help.

Share the required documents with the team member.

Arrange a required training session for the team member.

Raise this issue in the next team meeting and ask the rest of the team to clarify.

Give some advice to the team member to reduce their stress and anxiety.

Review team participation in the next retrospective meeting with all team members.

Reach out to the team member to discuss and address their concerns as soon as possible.

Evaluate upcoming project deadlines and reorganize team member assignments.

Record that the delay is attributable to the client and request a meeting.

Check the contractual terms about liquidated damages and reject if not applicable.

Meet with the sponsor to analyze the delays and the associated liquidated damages.

Schedule a detailed analysis of the delays using cause and effect.