PMP Practice Questions

An insurance company is executing a hybrid project to modernize their claims processing system. Infrastructure and security hardening follow a predictive approach with stage gates, while claims processing features are delivered in two-week sprints with regular customer demos. During a retrospective, the development team expresses frustration that they frequently wait for infrastructure approvals that delay their ability to deploy completed features. The infrastructure team explains their governance process requires formal change advisory board reviews that occur monthly. What is the best approach to address this impediment?

July 20, 2026

A retail company is implementing a hybrid project for a new inventory management system. The data migration follows a predictive schedule with specific cutover dates, while new features are developed using Kanban with continuous flow. A critical quality issue is discovered in the data migration test environment that could delay the cutover by six weeks. The development team using Kanban has been consistently delivering new features every week. Several stakeholders suggest accelerating feature delivery to compensate for the data migration delay. What should the project manager do?

July 20, 2026

A healthcare organization is delivering a patient management system using a hybrid approach. Regulatory compliance components follow a waterfall methodology, while clinical workflow features are developed iteratively based on user feedback. During a quarterly steering committee meeting, executives request a comprehensive status report showing progress across both work streams. The adaptive team measures velocity and completed story points, while the predictive team tracks earned value and milestone completion. How should the project manager present this information?

July 20, 2026

A manufacturing company is executing a hybrid project to implement a new production line. The engineering design follows a predictive approach with defined milestones, while the software automation team uses Scrum with three-week sprints. The engineering team has just completed their design phase two weeks ahead of schedule. The automation team's product owner wants to immediately begin working on advanced features that depend on the completed design, even though their current sprint has two weeks remaining and focuses on basic functionality. What should the project manager recommend?

July 20, 2026

A financial services company is implementing a new customer portal using a hybrid approach. The predictive portion involves infrastructure setup and regulatory compliance documentation, while the adaptive portion covers user interface development with two-week iterations. During sprint planning, the infrastructure team reports they need three additional weeks to complete security certifications before the development team can begin integration testing. The project manager is concerned about the impact on the overall timeline. What should the project manager do first?

July 20, 2026

Your agile team has been performing well, but three team members will be leaving for a major industry conference during the next sprint. The remaining five team members suggest they can maintain the same velocity by working longer hours to compensate. The product owner supports this idea as there are critical features needed for an upcoming release. One team member mentions they have personal commitments and cannot work extra hours. What is the best approach to handle this situation?

July 20, 2026

Your cross-functional agile team includes developers, testers, and a UX designer. The UX designer, who recently joined from a waterfall environment, typically works independently and presents completed designs for the team to implement. Developers have begun expressing frustration that designs don't consider technical constraints, leading to rework. The designer feels the developers don't respect the design process. Team collaboration is suffering. What action should you take to improve this situation?

July 20, 2026

During sprint planning, your development team commits to 45 story points based on their historical velocity. However, the product owner is frustrated because stakeholders are pressuring for more features to be delivered faster. The product owner asks you to challenge the team to commit to 60 story points this sprint, arguing that the team needs to 'push themselves' and that previous sprints didn't have enough urgency. The team appears uncomfortable with this request. How should you respond?

July 20, 2026

Your agile team has consistently delivered increments on time for the past four sprints. However, you notice during daily standups that one team member, Sarah, rarely speaks and only provides minimal updates. When she does contribute, her ideas are often valuable but she seems hesitant. Other team members are more vocal and sometimes talk over quieter members. The team velocity is good, but you're concerned about full team engagement. What is the most effective approach to ensure all voices are heard?

July 20, 2026

You are leading an agile team that has been together for three sprints. During the latest retrospective, two team members had a heated argument about code review practices. One developer believes all code should be reviewed before merging, while another argues this slows down delivery. The tension is affecting team morale, and other team members are becoming uncomfortable. Several people remained silent during the rest of the retrospective. What should you do first to address this situation?

July 20, 2026

Your agile project has been using relative estimation with story points for six months. A new senior stakeholder joins and demands to know exactly when specific features will be delivered, expressing frustration with 'vague agile estimates.' They insist the team provide hour-based estimates and commit to fixed delivery dates for features, stating that their previous projects always worked this way successfully. The team's velocity has been stable at 30-35 points per sprint, and they have a well-groomed backlog. The stakeholder threatens to escalate to executive leadership if you cannot provide 'real project management.' How should you respond?

July 20, 2026

During a sprint retrospective, your team identifies that they spent 40% of the sprint fixing production defects that escaped from previous sprints rather than working on new features. The team proposes adding a 'quality sprint' every third sprint where they do no new development and only focus on fixing technical debt and improving test coverage. The product owner objects, stating this will reduce feature delivery by 33% and jeopardize committed roadmap dates. The team argues they cannot maintain quality with the current pace. How should you facilitate resolution of this conflict?

July 20, 2026

Your organization is running multiple agile teams working on different components of an integrated product. Each team has its own product owner who prioritizes their component backlog independently. During integration testing, you discover that Team A built a feature assuming a specific API structure, while Team B simultaneously changed that API for their own feature—neither team coordinated. This is the third time in two months that integration issues have occurred due to lack of coordination. The teams meet their individual sprint goals but integrated product releases are delayed. What is the MOST effective solution?

July 20, 2026

You are leading an agile transformation for a product team that has just completed their third sprint. The Definition of Done (DoD) requires automated testing, code review, and deployment to staging environment. During sprint planning, the team consistently over-commits because they estimate story points based on development effort only, not accounting for DoD activities. As a result, several stories are left incomplete each sprint, with testing and code review pushed to the next sprint. Technical debt is accumulating, and the product owner is frustrated with low velocity. What is the BEST approach to address this situation?

July 20, 2026

Your agile team has been working on a mobile application for six sprints. During the latest sprint review, the product owner suddenly realizes that a core feature the team built in Sprint 3 doesn't align with the evolving market needs discovered through recent customer interviews. The feature took considerable effort to build and is technically sound, but customer feedback indicates it provides minimal value. The product owner wants to remove it from the product and pivot to features customers actually need. Some team members are resistant, feeling their work was wasted. What should you do as the Scrum Master?

July 20, 2026

You are managing a hybrid transformation project where the organization is transitioning from waterfall to agile for product development while maintaining waterfall for regulatory compliance activities. The transformation is halfway complete, and you're facing significant resistance from middle managers who fear their roles will become obsolete. Two managers have been actively undermining the agile teams by withholding resources and questioning their decisions in executive meetings. Team velocity has dropped 30%, and several key team members are considering leaving. The executive sponsor supports the transformation but is frustrated with the slow progress. What is your best course of action to address this resistance?

July 20, 2026

Your hybrid project team includes highly experienced senior engineers who prefer the waterfall approach and early-career developers who are enthusiastic about agile practices. During retrospectives, the senior engineers dominate conversations, dismissing agile ceremonies as 'overhead' and suggesting the team should 'just focus on coding.' The junior developers have stopped participating actively, and you've noticed their engagement scores dropping. One junior developer privately tells you they feel their ideas aren't valued. The project is delivering on schedule, but you're concerned about long-term team health and knowledge transfer. How should you address this team dynamic?

July 20, 2026

You are leading a hybrid project with a remote team distributed across four time zones. The agile workstreams use daily standups and pair programming, while the waterfall workstreams rely on weekly status meetings and detailed documentation. Several team members from the waterfall workstream have complained that they feel excluded from decision-making and don't understand what the agile team is building. Meanwhile, agile team members are frustrated by slow feedback loops from the waterfall team. You notice that informal communication happens primarily within each workstream but rarely across them. What is the most effective strategy to build a cohesive team culture?

July 20, 2026

Your organization is piloting hybrid project management on a critical product launch. The waterfall-oriented governance board requires detailed scope documentation and change control, while your agile development team insists on responding to emerging customer needs without bureaucratic delays. During a recent sprint review, the team demonstrated features that deviated from the approved scope baseline, leading to a tense conversation with executives who feel the project is out of control. The development team argues that the changes deliver better customer value based on recent user research. As the project manager, how should you bridge this cultural divide?

July 20, 2026

You are managing a hybrid project where the development team works in two-week sprints while the infrastructure team follows a waterfall approach with phase gates. During sprint planning, the development team commits to features that require infrastructure changes, but the infrastructure team is still in the design phase and cannot commit to delivery dates. This misalignment has caused three consecutive sprints to end with incomplete work. Team morale is declining, and stakeholders are questioning the project's viability. What should you do first to address this systemic issue?

July 20, 2026

You are facilitating sprint planning for a web development team. The product owner has prioritized 15 user stories for the upcoming sprint, but based on the team's velocity from the past three sprints (averaging 34 story points), this represents 52 story points of work. Several team members express concern about overcommitment. The product owner insists all stories are important and should be included. How should you proceed?

July 20, 2026

Your agile team is working on a healthcare application project. A critical regulatory requirement emerges mid-sprint that must be implemented before the product can be released. The team has already committed to several user stories for the current two-week sprint and is on track to complete them. The new requirement will take approximately one week of effort. What is the best approach to handle this situation?

July 20, 2026

You are the product owner for an e-commerce platform development project. The development team has completed several user stories related to the shopping cart functionality. During the sprint review, you notice that while the features work technically, they don't fully align with the customer experience you envisioned based on recent user feedback. The team is asking you to accept the stories as done. What should you do?

July 20, 2026

Your agile team has just completed their third sprint of a mobile app development project. During the sprint retrospective, team members express frustration that they keep discovering new technical dependencies mid-sprint, causing them to miss their sprint commitments. The team wants to improve their planning process. What should the team do first to address this issue?

July 20, 2026

You are managing a software development project using Scrum. During the daily standup, one team member mentions they are blocked because they are waiting for clarification from the product owner on a user story acceptance criterion. The product owner is not present at the standup meeting. Another team member suggests moving forward with their best interpretation of the requirement. What should you do as the Scrum Master?

July 20, 2026