PMP Practice Questions

You are managing a predictive construction project to build a new hospital wing with a 36-month timeline and $45M budget. Your team of 40 members includes architects, engineers, contractors, and hospital operational staff. At the 18-month mark, during earned value analysis, you identify that CPI is 0.92 and SPI is 0.88. In reviewing team performance data, you notice that the top 20% of your team members are producing 60% of the project value, while several team members are consistently underperforming against their assigned tasks. The human resource management plan includes a performance measurement approach, but you have not conducted formal performance reviews due to project pressures. Several stakeholders have commented on specific individuals not meeting expectations. Union agreements require 90-day notice for any personnel changes. What should you prioritize?

September 29, 2026

You are managing a predictive pharmaceutical project developing a new drug delivery system with a fixed 18-month regulatory submission deadline. Your team includes research scientists, regulatory specialists, and manufacturing engineers. Six months into the project, you notice that the scientists are creating highly detailed technical documentation that far exceeds regulatory requirements, while the regulatory team complains this slows down their review process. The scientists argue that thorough documentation is part of their professional standards. Meanwhile, manufacturing engineers are waiting for finalized specifications to begin their work, and this path is now on the critical path with only two weeks of float remaining. The quality management plan specifies documentation standards that the scientists are exceeding. How should you address this situation?

September 29, 2026

You are managing a multi-year predictive ERP implementation project for a global manufacturing company. The project organizational chart shows a matrixed structure where team members report both to you and their functional managers. Three months into execution, you discover that five critical team members are consistently being pulled back to operations by their functional managers to address production issues, causing them to miss 40% of their planned project hours. This has resulted in two successive missed milestones. You have raised this issue in the last two steering committee meetings, but functional managers argue that production takes priority. The project charter clearly states resource commitment levels, and the sponsor supported the project publicly but has not intervened. What should be your next step?

September 29, 2026

You are leading a predictive aerospace project with strict quality gates and regulatory requirements. Your project team of 25 members has been working together for nine months. During a critical design review, you notice that two senior engineers from different functional departments consistently undermine each other's technical approaches in meetings, creating tension that is now affecting team morale. Other team members have started taking sides, and collaboration has noticeably decreased. The project sponsor mentions that both engineers are highly regarded in the organization and have worked together on previous projects without issues. You have a major milestone deliverable due in four weeks that requires their joint contribution. What is the most effective approach?

September 29, 2026

You are managing a large government infrastructure project using a predictive approach with a 24-month timeline. During month 8, your technical lead submits his resignation, citing personal reasons. This individual has deep knowledge of legacy systems that interface with your new solution, and no documentation exists for these integrations. The resource manager offers you two options: promote a junior team member who has been shadowing the technical lead for three months, or bring in an external consultant with general expertise but no project-specific knowledge. Your project is currently on schedule, but the next phase involves critical integration work starting in six weeks. What should you do first?

September 29, 2026

You are facilitating a sprint retrospective for a team that has just completed a challenging sprint where they missed their sprint goal. During the retrospective, two team members begin blaming each other for technical decisions that led to delays. Other team members become defensive, and the conversation is deteriorating into personal criticism rather than focusing on process improvement. The team has worked well together in the past, but the pressure of the missed goal is creating tension. As the facilitator, what should you do?

September 29, 2026

Your Kanban team has been tracking their flow metrics, and you notice the average cycle time has increased from 4 days to 7 days over the past month. The team's WIP limits haven't changed, and the work item types are consistent with previous months. During a team discussion, you discover that items are spending significantly more time in the 'Code Review' column, often waiting 2-3 days before being reviewed. Team members mention they're focused on completing their own work before reviewing others' contributions. What should the team do to address this issue?

September 29, 2026

Your agile team is three sprints into developing a mobile application. During the latest sprint review, stakeholders provide feedback that the user interface doesn't match their expectations, even though the implemented features match the acceptance criteria in the user stories. The Product Owner explains they wrote the acceptance criteria based on their understanding but didn't include UI specifications. The team is frustrated because they'll need to rework completed features. How should this situation be addressed going forward?

September 29, 2026

During sprint planning, your development team is struggling to break down a large user story estimated at 21 story points. The Product Owner insists this story must be completed in the upcoming two-week sprint because it's critical for an upcoming trade show demonstration. The team expresses concern that they typically complete 25-30 story points per sprint, but this single story would consume most of their capacity and carries significant technical risk. The story cannot be demonstrated partially. What is the best approach?

September 29, 2026

Your Scrum team has completed their third sprint, and the Product Owner notices that the team's velocity has been inconsistent: 21 story points in Sprint 1, 15 in Sprint 2, and 18 in Sprint 3. The Product Owner is concerned about meeting the release deadline and asks you, as the Scrum Master, to commit to a specific velocity for the remaining sprints so stakeholders can plan accordingly. The team is still learning to work together and refining their estimation practices. What should you do?

September 29, 2026

You are managing a pharmaceutical research project following a stage-gate predictive methodology. Your project has just completed the design phase, and you are preparing for the gate review before entering the development phase. During preparation, you discover that one of the key assumptions documented in the project charter—that a specific research facility would be available—is no longer valid due to facility renovations. The next available equivalent facility is in a different location and would increase project costs by 8%. What should you do BEFORE the gate review?

September 29, 2026

You are managing a large infrastructure project with multiple subcontractors. One of your key vendors has completed their deliverable, and you are conducting procurement closure activities. While reviewing the final deliverable, you notice it meets all technical specifications in the contract, but the vendor failed to submit three required progress reports during execution as stipulated in the contract terms. The vendor is requesting final payment and contract closure. What is the MOST appropriate action?

September 29, 2026

You are managing a software implementation project for a financial institution using a waterfall approach. During quality testing, the QA team discovers that 12% of test cases are failing, primarily related to security authentication features. The quality management plan specified that no more than 5% of test cases should fail at this stage. The development team believes they can fix the issues within one week, but this will delay the scheduled user acceptance testing. What should you do?

September 29, 2026

Your manufacturing project is in the planning phase, and you are developing the cost baseline. You have completed bottom-up estimating for all work packages and have aggregated these costs. The finance department requires a 10% management reserve for organizational risks, and historical data shows similar projects typically experience 15% cost variance. Your project sponsor asks what the final project budget should include. What is the MOST appropriate approach?

September 29, 2026

You are managing a construction project using a predictive approach. During the execution phase, a key supplier informs you that critical materials will be delayed by three weeks due to manufacturing issues. The delay will impact the critical path and push the project completion date beyond the contractually agreed deadline. Several team members suggest crashing the schedule by adding overtime resources, while the sponsor wants to explore fast-tracking options. What should you do FIRST?

September 29, 2026

You are coaching a newly formed agile team that includes three junior developers and two senior developers. During the first two sprints, you notice the senior developers are completing most of the complex stories while junior developers are assigned only simple tasks. The senior developers say they are trying to help the team meet commitments, but the junior developers express frustration in private that they are not learning new skills. Sprint goals are being met, but you are concerned about long-term team capability and sustainability. What is the best approach?

September 29, 2026

Your agile team has two developers who consistently clash during daily standups and sprint planning. One developer prefers thoroughly discussing technical approaches before committing to work, while the other prefers to start coding quickly and iterate. Their disagreements are starting to affect team dynamics, with other team members avoiding engaging in technical discussions. Both developers are highly skilled and their work quality is excellent. Yesterday, their disagreement during refinement caused the session to run 30 minutes over time. What should you do?

September 29, 2026

During a sprint review, a key stakeholder becomes visibly upset when seeing the increment, stating that the features demonstrated are not what they expected, even though the stories were approved during sprint planning. The product owner defends the work, saying the team delivered exactly what was written in the user stories. The stakeholder insists the team must redo the work. Team morale drops immediately as they feel their hard work is being dismissed. How should you address this conflict?

September 29, 2026

Your agile development team includes members from four different countries across three time zones. During sprint planning, you notice that team members in the Asia-Pacific region rarely speak up, while team members in North America dominate the conversation. The sprint retrospectives show similar patterns. The team's velocity has been declining over the past two sprints, and some stories are being carried over because requirements were misunderstood. What is the most effective action to improve team collaboration?

September 29, 2026

You are leading an agile project team that has been working together for three sprints. During the latest retrospective, several team members express frustration that decisions are often delayed because they feel they need to wait for your approval on minor implementation details. The team has strong technical skills and has consistently met their sprint commitments. Team velocity is stable, but you notice team members seem hesitant to self-organize. What should you do to address this situation?

September 29, 2026

You are leading a regulatory compliance project using a hybrid approach where legal reviews follow predictive gates and process implementation uses iterative delivery. A new compliance regulation is announced mid-project that significantly impacts scope. The legal team insists on a complete requirements freeze and full impact analysis before proceeding (6-8 weeks), following their standard risk management protocol. The implementation team wants to continue iterating on unaffected areas and adapt as legal analysis progresses. The compliance deadline is regulatory-mandated and cannot move. Both teams believe their approach protects the organization, and tension is escalating. Several implementation team members have complained that legal is 'blocking progress,' while legal counsel has expressed concerns about 'reckless iteration' on compliance matters. What is your BEST course of action?

September 29, 2026

Your hybrid project includes an offshore agile development team and an onshore predictive implementation team. The agile team's Scrum Master has been highly effective, and team members openly share impediments and collaborate well. However, you've noticed in the predictive workstream that team members rarely speak up in status meetings, several risks weren't reported until they became issues, and there's high reliance on formal change control processes even for minor decisions. The predictive team lead is experienced but tends to make decisions unilaterally. Cultural assessments show the offshore team comes from a high power-distance culture while the predictive team reflects the corporate risk-averse culture. What should you do to create greater psychological safety across both workstreams?

September 29, 2026

You are managing a product development initiative using a hybrid approach where hardware follows a stage-gate predictive model and software uses Scrum. During integration testing, a critical hardware defect is discovered that requires three months to redesign and remanufacture—extending beyond the current software release schedule. The software team has already completed features dependent on the hardware specifications and wants to continue with new features. The hardware team is demoralized by the setback and feeling blamed. Senior management is pressuring you to maintain the original launch date. How should you lead the teams through this challenge?

September 29, 2026

Your organization is piloting agile practices within traditionally predictive portfolios. You're leading a hybrid project with a co-located agile team and distributed predictive workstreams across three continents. After four months, you notice the agile team has strong cohesion and high performance, but the distributed predictive teams report feeling disconnected and undervalued. Several key resources from the predictive workstreams have requested transfers, citing lack of engagement. Executive stakeholders are questioning whether the hybrid approach is sustainable. What is the MOST effective way to address this disparity?

September 29, 2026

You are managing a hybrid project where the development team uses Scrum while the compliance and regulatory workstreams follow a predictive approach. During sprint planning, a senior compliance officer insists on attending all Scrum ceremonies and has been providing detailed instructions to developers, effectively bypassing the Product Owner. Team velocity has dropped 30% over two sprints, and developers privately express frustration about conflicting priorities. The compliance officer believes their involvement is necessary due to regulatory risks. How should you address this situation?

September 29, 2026