Practice Questions
PMP Practice Questions
Scenario-based questions aligned with the 2026 PMP Exam Content Outline. All questions reviewed by a certified PMP before publishing.
245 questions found · page 1 of 10
You are managing a high-stakes hybrid project with a fixed regulatory deadline. The core development uses Scrum, while compliance documentation follows a stage-gate process. Two months from the deadline, your most experienced developer, James, who understands both the technical and regulatory requirements, gives two weeks' notice. He is irreplaceable in the timeline remaining. The team is already at maximum capacity. James mentions he's leaving because he feels the organization doesn't value his contributions despite his critical role. What is your most important immediate action?
October 9, 2026
Your organization is transitioning to hybrid delivery. You are managing a pilot project with both predictive and agile components. The project steering committee, composed of executives unfamiliar with agile, insists on detailed monthly status reports showing percent complete for all work packages, including the agile sprints. Your agile team lead argues this contradicts agile principles and will force the team to waste time on meaningless estimates. The steering committee controls project funding and has expressed concern about the "lack of visibility" into agile work. How should you address this situation?
October 9, 2026
You are leading a transformation program using a hybrid approach. Three months in, you notice that Maria, a senior business analyst on the predictive track, consistently delivers exceptional requirements documentation but frequently criticizes the agile team's "incomplete" user stories in cross-functional meetings. The agile product owner has stopped inviting Maria to refinement sessions, creating a silo. Maria has 20 years of experience and is technically correct that user stories lack the detail of traditional requirements. However, her approach is damaging collaboration. What should you do?
October 9, 2026
Your hybrid project has a distributed team across four time zones. The predictive workstream team meets face-to-face weekly and has strong cohesion. The agile workstream operates virtually with daily standups but team members rarely interact beyond ceremonies. Velocity has plateaued, and retrospectives reveal team members feel disconnected. The agile coach suggests mandatory video-on policies and virtual team-building activities. Several senior developers privately tell you they find these activities juvenile and prefer focusing on work. What is the best approach to improve team cohesion?
October 9, 2026
You are managing a hybrid project where the infrastructure team uses waterfall and the application development team uses Scrum. During sprint planning, the development team commits to features requiring network configuration changes. The infrastructure team, working from a fixed schedule defined six months ago, informs you they cannot accommodate the changes until next quarter. The development team is frustrated and threatens to escalate to executives. Stakeholders expect the features in three weeks. What should you do first?
October 9, 2026
You're managing a hybrid project to modernize a legacy system. Phase 1 (months 1-4) uses predictive approach for infrastructure and data architecture, while Phase 2 (months 5-10) uses Scrum for application development. You're now in month 3, and the infrastructure team has encountered unexpected complexity that will delay their completion by 6 weeks, pushing into month 5.5. The development team's sprint 0 is scheduled for month 5, and team members are already assigned. Waiting would idle 8 developers for 6 weeks at $180K cost. The development team suggests they could begin working on independent modules using simulated infrastructure. What factors should most heavily influence your decision?
October 6, 2026
Your hybrid project combines predictive hardware development with agile firmware iterations. The hardware team has completed their design phase and moved into manufacturing (month 8 of 14), while the firmware team is in sprint 12 of 20. During sprint 12, the firmware team discovers that achieving optimal performance requires a minor hardware modification that would cost $45K and delay manufacturing by 3 weeks. Without this change, the product will meet minimum specifications but perform 25% slower than competitors. The product owner wants to make the change, but the hardware lead argues the decision should follow the formal change control process with steering committee approval, which meets monthly. What should you do?
October 6, 2026
You're leading a digital transformation project using a hybrid approach where compliance and regulatory work follows predictive planning, while customer-facing features are developed iteratively. During the fifth sprint review, the product owner and development team demonstrate working features, but the compliance officer identifies that three completed user stories don't meet regulatory requirements that were documented in the initial project charter. The team claims they followed the acceptance criteria in the user stories. The compliance deliverables are managed separately and weren't scheduled for integration testing until next month. What is the root cause you should address?
October 6, 2026
Your organization is implementing a new ERP system using a hybrid approach: data migration and infrastructure use waterfall phases, while business process configuration uses iterative cycles. After the second iteration, stakeholders from finance request significant changes to the chart of accounts structure, which impacts both the completed data migration design and upcoming infrastructure specifications. The change would add substantial business value but requires rework across both predictive and adaptive streams. The project is at 40% completion with moderate schedule pressure. How should you proceed?
October 6, 2026
You are managing a hybrid project where the infrastructure team works in predictive mode with a 6-month timeline, while the application development team uses 2-week Scrum sprints. During sprint planning, the development team commits to features that depend on infrastructure components scheduled for delivery in month 5. The infrastructure team is currently on track but has no buffer. The development team argues they need these features in sprint 8 (month 4) to meet a critical market window. What should you do first?
October 6, 2026
You are managing a product development project using a hybrid approach. The UX design work follows a phase-gate process to ensure brand consistency, while development uses Scrum. During Sprint 5, a major competitor launches a similar product with a feature your team planned for Sprint 8. The product owner wants to reprioritize immediately and skip the UX design review to accelerate delivery. The UX lead insists that bypassing the design process will create technical debt and brand inconsistency. Both are escalating to you. What is your best course of action?
October 4, 2026
Your organization is piloting a hybrid approach on a strategic initiative. The predictive-focused PMO requires detailed monthly status reports with earned value metrics, while your agile team tracks progress through burndown charts and sprint reviews. Team members are spending six hours per month translating their agile metrics into PMO templates, and they're frustrated by what they perceive as duplicative reporting. The PMO director insists on standardized reporting for portfolio visibility. How should you address this situation?
October 4, 2026
You are leading a hybrid project where regulatory compliance work follows a waterfall approach due to audit requirements, while new feature development uses Kanban. A senior developer who excels at iterative development has been assigned to document compliance procedures, a predictive task requiring detailed upfront planning. The developer is frustrated, producing low-quality documentation, and has privately expressed feeling underutilized. Meanwhile, a compliance specialist is struggling with the ambiguity of Kanban flow. What should you do?
October 4, 2026
Your hybrid project team includes five co-located developers working in two-week sprints and three distributed subject matter experts who contribute according to a predictive schedule with monthly milestones. The SMEs have missed two consecutive touchpoints, causing the development team to make assumptions that later required rework. The SMEs claim they were unaware of the specific timing of developer needs. You need to improve team cohesion and reduce waste. What is the most effective approach?
October 4, 2026
You are managing a hybrid project where the development team uses Scrum for product features while the infrastructure team follows a waterfall approach. During sprint planning, the development team commits to delivering a new customer portal feature. However, the infrastructure team later reports they cannot provision the required cloud servers until their phase-gate approval is completed in three weeks, which will cause the sprint goal to fail. Team morale is declining as developers feel blocked. What should you do first?
October 4, 2026
Your organization is executing a hybrid project to implement a new financial system. The software configuration follows an adaptive approach with two-week iterations, while data migration and cutover activities are planned predictively due to strict regulatory windows. You're currently in iteration 5 of 10. During a governance review, the CFO requests a detailed status report showing percentage complete for the entire project and exact completion dates for all remaining work. Your adaptive team tracks progress using velocity and burndown charts. How should you respond to this request?
September 30, 2026
You're managing a product development project using a hybrid approach where research and design follow a stage-gate process, while development and testing use Scrum. The design team has just completed the design phase and handed off detailed specifications to the development team. During sprint planning, the development team identifies several design elements that are technically infeasible with current technology and proposes alternative approaches that would require design changes. The design lead is resistant, stating that the design was approved through the formal gate review and shouldn't change without going back through governance. What should you do?
September 30, 2026
You are leading a hybrid project where marketing campaigns follow a waterfall approach with fixed launch dates, while the supporting digital platform is developed using Kanban. The platform team has adopted a continuous flow model and deploys features as they're completed. The marketing director is frustrated because features are being released without coordination with campaign timelines, resulting in promotional materials that don't match current functionality. The platform team argues that continuous delivery provides faster value. What is the best way to resolve this conflict?
September 30, 2026
Your hybrid project uses iterative development for customer-facing features and predictive planning for regulatory compliance activities. During a retrospective, the development team reports that compliance reviews are causing significant delays because compliance work is scheduled in sequential phases without team input. The compliance manager insists on following the approved plan to ensure audit readiness. Team morale is declining as they feel the rigid compliance process contradicts the adaptive approach they use for features. How should you address this situation?
September 30, 2026
You are managing a hybrid project where the development team uses Scrum for software components while infrastructure deployment follows a predictive approach. The software team has completed three sprints successfully, but the infrastructure team is two weeks behind schedule due to unexpected vendor delays. Stakeholders are concerned about integration timelines. The next sprint planning meeting is in two days, and the infrastructure team's delay will impact the planned software features that depend on the new servers. What should you do first?
September 30, 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
