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 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

You are leading a hybrid project to modernize a manufacturing execution system. The data migration component follows a waterfall approach due to regulatory validation requirements, while new features are developed using Kanban. Three months into the project, your organization announces a merger that will require integrating data from the acquired company's systems - significantly expanding the data migration scope. The Kanban team has been delivering features steadily, but these features depend on the data migration being complete. The project budget is fixed, and the regulatory validation timeline cannot be compressed. Senior management wants to know how you will handle this change without delaying time-to-market. What is the BEST approach?

September 18, 2026

You are managing a hybrid product development project where the hardware components follow a predictive approach with a 12-month timeline, while the software team operates in 2-week sprints. The hardware team has just informed you that a critical component will be delayed by 6 weeks due to supply chain issues. This delay will impact the integration phase where both teams must work together. The software team has already completed 60% of their planned features and is on track. Several stakeholders are pressuring you to maintain the original go-live date. What should be your FIRST action to address this situation?

September 16, 2026

You are managing a pharmaceutical product launch project using a hybrid approach. Clinical trials and regulatory submissions follow a stage-gate predictive model due to FDA requirements, while the marketing campaign and digital presence are developed using Scrum. The regulatory team has just learned that the FDA will require an additional study, delaying approval by 9 months. Meanwhile, the Scrum team has completed the e-commerce platform, mobile app, and digital marketing materials scheduled for the original launch date. The program sponsor is concerned about losing competitive advantage and wants options for generating value from the completed digital work. What is the MOST appropriate strategy?

September 16, 2026

Your hybrid construction and technology project involves building a new data center facility (predictive) while simultaneously developing the cloud management platform (agile). The construction phase has clearly defined milestones tied to building permits and inspections. The software team works in 3-week sprints and has been delivering features ahead of schedule. A major stakeholder from the facilities group has started attending sprint reviews and is now requesting detailed Gantt charts for the software deliverables, claiming they need predictability to coordinate facility operations planning. The software team feels this contradicts agile principles and will slow them down with unnecessary documentation. The stakeholder insists they cannot plan operations without concrete dates. What should you do to resolve this conflict?

September 16, 2026

Your organization is implementing a new customer portal using a hybrid approach. The infrastructure and security components are being delivered predictively with detailed requirements and regulatory compliance needs, while the user interface and customer-facing features are developed using Scrum. During the third sprint review, the Product Owner accepts several UI features, but the security team identifies that these features cannot be deployed to production because the underlying security framework (managed predictively) won't be ready for another two months. The development team is frustrated that completed work cannot be released, and the Product Owner is concerned about demonstrating value to stakeholders. How should you address this situation going forward?

September 16, 2026

Your hybrid project team includes contractors who are deeply familiar with the legacy system (managed predictively) and permanent employees who are newer but working on the agile modernization effort. During planning, you notice the contractors dominate technical discussions and the permanent employees defer to them, even though the employees will maintain the new system long-term. The contractors are scheduled to roll off in three months. Knowledge transfer was included in the project plan but hasn't been prioritized due to schedule pressure. What should you do?

September 11, 2026

You're managing a product development project using a hybrid approach where UX research follows Kanban while engineering uses Scrum. Two team members—a UX researcher and a software engineer—have had escalating disagreements about research timing and findings. The researcher believes the engineer dismisses user insights, while the engineer feels research is delivered too late to influence sprint planning. Both are technically excellent but their conflict is creating tension in cross-functional planning sessions. Other team members are starting to take sides. What is the most effective way to address this conflict?

September 11, 2026

Your hybrid project combines agile development sprints with stage-gated regulatory approvals. A high-performing senior developer has become increasingly disengaged after being denied a promotion due to budget constraints. She has begun missing daily standups and her code review quality has declined. Other team members have noticed and morale is affected. The predictive workstream manager suggests documenting performance issues formally. You have a 1-on-1 scheduled with her tomorrow. What is your best approach?

September 11, 2026

You're leading a hybrid transformation project where 40% of team members are co-located and 60% are distributed across three time zones. During retrospectives, the remote team members have been unusually quiet, and anonymous feedback reveals they feel their opinions are less valued than those of co-located staff. The co-located team leads tend to have side conversations that exclude remote participants. Despite this, sprint commitments are being met. A key stakeholder suggests this isn't a priority since delivery metrics are satisfactory. How should you respond?

September 11, 2026

You are managing a hybrid project where the development team uses Scrum while the infrastructure team follows a predictive approach. Recently, several infrastructure team members have expressed frustration that they are being excluded from sprint reviews and feel disconnected from the product vision. The development team argues that including infrastructure in reviews slows down their feedback cycles. Team velocity has started declining, and integration issues are increasing. What should you do first to address this situation?

September 11, 2026

Your organization is transitioning a large, multi-year infrastructure program to agile delivery. The program consists of five interdependent product teams, each running two-week sprints. After three program increments, dependencies between teams are causing frequent delays—Team A cannot complete their sprint commitments because they're waiting for API specifications from Team B, while Team C's database changes block Team D's integration testing. The program board shows 47 active dependencies across teams. Teams are becoming frustrated with blocked work and declining morale. What approach would best address these systemic dependency issues?

September 9, 2026

An agile team developing a healthcare platform has maintained consistent velocity at 38 story points for six consecutive sprints. During the retrospective, technical debt items are repeatedly raised but never addressed because the product owner prioritizes new features to maintain competitive advantage. The lead architect warns that accumulated technical debt is increasing the time required for new features by approximately 30%, and estimates two full sprints would be needed to address critical technical debt. Code quality metrics show increasing defect rates and decreasing test coverage. What is the most appropriate action?

September 9, 2026

A distributed agile team across four time zones is developing an API integration platform. During the daily standup conducted via video conference, developers in the Asia-Pacific region consistently remain silent or provide minimal updates. The product owner mentions that several critical defects discovered by APAC developers were not communicated until the weekly status report, causing a two-day delay in resolution. Team velocity metrics show APAC contributions are significantly lower than other regions despite having equal headcount. What is the most effective approach to improve team collaboration and information flow?

September 9, 2026

Your agile team has completed three sprints of a mobile application project. The product owner consistently adds new acceptance criteria during sprint reviews, claiming these represent newly discovered customer needs. The team's velocity has dropped from 45 to 28 story points, and team members are frustrated with rework. The product owner insists all changes are critical for market competitiveness. Sprint planning for the next iteration is scheduled for tomorrow. What should the Scrum Master do first to address this situation?

September 9, 2026

During the eighth sprint of a financial services product, a regulatory compliance requirement emerges that affects the system's data retention architecture. The compliance officer estimates implementation requires 320 hours of effort, equivalent to four full sprints of the eight-person team's capacity. The product owner has a committed release date in six sprints to support a major client contract worth $2.3M annually. The current product backlog contains 180 story points of features promised for this release. The team's average velocity is 45 story points per sprint. How should the team approach this situation?

September 9, 2026