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.
35 questions found · page 1 of 2
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
Your agile team is building an e-commerce platform. At the sprint review, the team demonstrates a completed shopping cart feature to stakeholders. The functionality works as specified in the user story, but the product owner notices the user interface colors don't match the company's recently updated brand guidelines, which changed during the sprint. What should happen next?
June 22, 2026
You are facilitating sprint planning for a three-week sprint. The product owner presents the prioritized backlog, and the team begins selecting user stories. After selecting six stories totaling 24 story points, three team members mention they have committed to attending a mandatory company training program that will take them away for three full days during the sprint. What should the team do?
June 22, 2026
During a sprint retrospective for your software development project, team members identify that unclear user story acceptance criteria have caused significant rework in the past three sprints. The team estimates that 30% of their time has been spent redoing work that didn't meet unstated expectations. What should the team do to address this issue?
June 22, 2026
Your agile team is developing a customer relationship management (CRM) system. The product owner has created a prioritized product backlog with 45 user stories. Several stakeholders are asking when specific features will be delivered. The team has completed two sprints, delivering 12 and 11 story points respectively. What is the best way to provide stakeholders with delivery expectations?
June 22, 2026
You are leading an agile project to develop a mobile banking application. The team has just completed Sprint Planning and committed to delivering eight user stories in the upcoming two-week sprint. During the daily standup on day three, a developer mentions that one of the stories is taking much longer than estimated and may not be completed. What should you do first?
June 22, 2026
Your distributed agile team spans three time zones with only a two-hour daily overlap. Sprint planning consistently runs over time, with the India-based developers joining at 6 AM their time and the US-based product owner available only until 11 AM EST. Retrospectives reveal that 40% of stories require significant rework because developers interpreted requirements differently than intended. The team has tried detailed acceptance criteria, but misunderstandings persist. Team velocity is 30% below similar co-located teams. What structural change would most effectively address this challenge?
June 10, 2026
During a release planning session for a regulated healthcare product, your compliance officer insists that all user stories must be fully documented with detailed requirements specifications before development begins, citing audit requirements. Your agile team argues this contradicts their working agreements and will create massive waste, as they've successfully used acceptance criteria and collaborative elaboration for 15 sprints. The compliance officer shows you audit findings from another division that was penalized for insufficient documentation. Your organization has no precedent for agile projects in regulated environments. How do you proceed?
June 10, 2026
Your product has been using two-week sprints successfully for eight months. Recently, market dynamics have accelerated, with competitors releasing features weekly. Your executive sponsor wants the team to switch to one-week sprints to 'move faster and be more agile.' The team is concerned this will increase ceremony overhead and reduce their actual development time. When you analyze the data, you find the team averages 1.5 days of ceremonies per sprint and typically doesn't have testable increments until day 9-10 of the current sprint. What recommendation best addresses the sponsor's concern while maintaining team effectiveness?
June 10, 2026
You're managing a complex product with three agile teams working on interdependent features. During sprint planning, Team A commits to a critical API that Teams B and C need by sprint day 7 to meet their commitments. On day 5, Team A discovers the API requires a third-party security review that takes 10 business days. Team A's scrum master suggests they'll finish other stories and carry the API to next sprint. Teams B and C will miss their sprint goals without this dependency. How should you handle this situation?
June 10, 2026
Your agile team has been delivering features every two weeks for six months. During the latest sprint review, a key stakeholder expresses frustration that the product increment doesn't align with their vision, despite approving stories throughout development. The product owner admits they've been accepting stories based on technical completion rather than business value validation. Technical debt has accumulated, and the team's velocity has dropped 30% over the last three sprints. What should you do first to address this systemic issue?
June 10, 2026