PMP Practice Questions

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