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.
70 questions found · page 2 of 3
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 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
An agile team working on a financial services application has maintained a consistent velocity of 28-32 story points over the past six sprints. During Sprint 7 planning, the team estimates several user stories and realizes they are consistently giving higher estimates than in previous sprints for similar work. When asked, team members mention they are concerned about upcoming regulatory requirements that might require rework, though the specific requirements won't be finalized until next quarter. The Product Owner is concerned that velocity is decreasing. What should the team do to address this situation?
July 7, 2026
A cross-functional agile team is building a data analytics platform. During Sprint 6, a critical production bug is discovered in functionality delivered two sprints ago that is affecting customer reporting. Fixing the bug will require approximately 13 story points of effort. The current sprint backlog contains 32 story points of planned work, matching the team's average velocity. The Product Owner wants to add the bug fix to the current sprint without removing any planned stories. What should the Scrum Master recommend?
July 7, 2026
An agile team is developing a customer relationship management (CRM) system. After the fourth sprint, the Product Owner reviews the increment during the sprint review and realizes that several features don't match what key stakeholders envisioned. The stakeholders are present and express concern that the product is heading in the wrong direction. The development team is frustrated because they built exactly what was described in the user stories. The team's definition of done includes code review, testing, and documentation. What is the most likely root cause of this issue?
July 7, 2026
A software development team is working on an e-commerce platform using two-week sprints. During sprint planning for Sprint 5, the Product Owner presents 15 user stories totaling 55 story points. Based on their velocity from the last three sprints (average: 34 story points), the team knows they cannot complete all stories. The Product Owner insists all stories are critical for an upcoming trade show demo in four weeks. The team is concerned about committing to work they cannot complete. What is the best approach for the team to take?
July 7, 2026
Your agile team has completed three sprints of a mobile application project. During the sprint retrospective, several team members express frustration that they are spending too much time in meetings and not enough time developing features. The Scrum Master notes that the team is attending daily standups, sprint planning, sprint reviews, sprint retrospectives, and several ad-hoc meetings called by stakeholders. Velocity has declined from 32 story points in Sprint 1 to 21 story points in Sprint 3. What should the Scrum Master do first to address this issue?
July 7, 2026
Your agile project to modernize a healthcare claims processing system has been running for five months with three-week sprints. The team has been successfully delivering functional increments, but you discover that the compliance officer has not been reviewing any deliverables because they were not included in sprint reviews. A regulatory audit is scheduled in six weeks, and the compliance officer now states that three completed features do not meet HIPAA requirements and cannot be deployed. The product owner is frustrated because compliance requirements were not in the original user stories. Rework will take approximately four sprints. What should be your primary focus to address this situation?
July 2, 2026
Your distributed agile team spans three time zones with six developers in India, four in Poland, and three in the United States. After six sprints, retrospective data shows that defect rates have increased by 40% and the team reports frustration with asynchronous communication. Most collaboration happens through written messages, and the daily standup rotates times weekly to accommodate all zones, resulting in inconvenient hours for different team members each week. Despite using collaborative tools, integration issues are discovered late. Team morale is declining. What structural change would most effectively address these delivery and collaboration challenges?
July 2, 2026
During a portfolio planning session, your organization has identified eight high-value initiatives for the next quarter, but only has capacity for five teams. The product owners are present and have sized their initiatives using story points. Three initiatives are strategic bets with uncertain outcomes, while five have clear customer demand and proven business cases. The CFO wants to maximize ROI by selecting the five safest initiatives. The CTO argues for including at least two strategic bets to drive innovation. As the agile practice lead, you need to recommend a portfolio approach. Which recommendation best applies agile principles to this portfolio decision?
July 2, 2026
You are leading an agile transformation for a financial services organization. After four months, three of your five scrum teams have adapted well, but two teams continue to struggle with completing their sprint commitments. Analysis shows these teams have significant dependencies on a legacy system team that works in two-week cycles but doesn't use agile practices. The legacy team cannot attend daily standups or sprint ceremonies due to their own schedule. This dependency causes delays in 60% of the struggling teams' stories. Senior management is pressuring you to show improved velocity metrics. What is the most effective approach to address this systemic impediment?
July 2, 2026
Your agile team has been working on a mobile banking application for three sprints. During the current sprint review, the product owner expresses dissatisfaction because the authentication feature doesn't match their vision, even though it meets all acceptance criteria that were discussed during sprint planning. The team completed all committed stories and the feature is technically sound. Several stakeholders at the review agree with the product owner's concerns. The product owner wants to reject the story and have it reworked immediately. What should you do first?
July 2, 2026
You are facilitating a sprint planning meeting for a three-week sprint. The product owner has presented the prioritized product backlog, and the team is discussing which user stories to commit to. One experienced developer suggests committing to 15 user stories, saying the team completed 12 last sprint and should push themselves. However, two team members will be on vacation for one week during this sprint. What should you do?
June 26, 2026
Your agile team has completed a sprint and is conducting a sprint review with stakeholders. During the review, a key stakeholder sees the working software for the first time and requests significant changes to the user interface, saying it doesn't match their expectations. The team completed all committed user stories and met the acceptance criteria as originally defined. The stakeholder insists these changes must be made immediately. How should you respond?
June 26, 2026
You are managing an agile software development project. The product owner has created a product backlog with 50 user stories but hasn't prioritized them yet. The development team is ready to start their first sprint planning meeting tomorrow. The product owner asks you what preparation is needed before the sprint planning session. What is the most important thing the product owner should do?
June 26, 2026
Your agile team is working on a website redesign project for a retail client. During the daily standup, one developer mentions she is blocked because she's waiting for design assets from the UI/UX designer, who is working on another high-priority task. The developer has been blocked for two days. The team has a sprint goal to complete three user stories by the end of the week. What should you do first as the Scrum Master?
June 26, 2026
You are leading an agile project to develop a mobile banking application. The team has just completed their second sprint and is preparing for the sprint retrospective. Several team members have mentioned challenges with the current definition of done, which seems unclear for certain user stories. As the project manager, you want to ensure the retrospective is productive and leads to actionable improvements. What should be the primary focus of this retrospective meeting?
June 26, 2026