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 3 of 3
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
You are facilitating a project using a hybrid approach where requirements are gathered upfront but development occurs in two-week iterations. After four iterations, the team's velocity has been inconsistent: 28, 15, 32, and 18 story points respectively. The team reports that some iterations include significant work on technical infrastructure that doesn't directly relate to user stories but is necessary for the architecture. The project sponsor is concerned about the unpredictable pace and asks why the team cannot maintain consistent velocity. How should you address this situation?
June 7, 2026
During the eighth sprint of a twelve-sprint project to build an e-learning platform, your team completes a sprint review. The product owner and key stakeholders attend the demonstration, and while they acknowledge the functionality works as specified in the acceptance criteria, they express concern that the user interface is more complex than they expected. They mention that teachers, the primary users, may struggle to navigate the system without extensive training. The team followed the user stories and acceptance criteria exactly as written. What should happen next?
June 7, 2026
Your Kanban team is experiencing flow problems on a data migration project. The team's board shows 15 items in the 'In Progress' column, 8 items in 'Code Review', and only 3 items in 'Done' over the past two weeks. Team members report feeling overwhelmed and context-switching frequently between multiple work items. Lead time for items has increased from an average of 5 days to 12 days. The team lead suggests adding more people to help clear the backlog. What is the most appropriate action to improve flow?
June 7, 2026
You are leading a Scrum team developing a customer relationship management (CRM) system. During sprint planning, the product owner presents a high-priority user story estimated at 21 story points, which exceeds the team's average velocity of 35 points per two-week sprint. The product owner insists this feature is critical for an upcoming sales conference in three weeks and must be completed in the next sprint. Several team members suggest breaking down the story, but the product owner argues that all components must be delivered together to be valuable. How should you proceed?
June 7, 2026
Your agile team has completed three sprints of a mobile application development project. During the sprint retrospective, team members express frustration that they frequently discover integration issues late in the sprint when merging code. These issues require significant rework and have caused the team to miss their sprint goals in two of the last three sprints. The team asks for your guidance on how to address this recurring problem. What should you recommend?
June 7, 2026
Your development team has been consistently achieving their sprint goals for the past four sprints with a stable velocity of 30 story points. In sprint planning for the next iteration, the team commits to 30 points of work. However, by mid-sprint during the daily standup, it becomes clear that three critical stories are blocked due to an unexpected production outage requiring immediate team attention. The team estimates they can only complete 18 points this sprint. What should the scrum master do?
May 29, 2026
Your scrum team is working on a healthcare application where regulatory compliance is critical. During the sprint, a team member discovers that a completed story from the previous sprint doesn't meet new HIPAA requirements that were recently clarified by the compliance department. The feature is already in the staging environment and was demonstrated to stakeholders. The Definition of Done includes 'meets all regulatory requirements,' but this specific requirement wasn't known during development. What should the scrum master facilitate?
May 29, 2026
During a sprint review, stakeholders see the completed user stories but express disappointment that the features don't match their expectations. The team followed the acceptance criteria precisely, and all stories meet the Definition of Done. The product owner approved the stories during backlog refinement two weeks ago. Stakeholders now request significant changes that would require reworking most of the sprint's output. What is the most appropriate next step?
May 29, 2026
You are facilitating sprint planning for a new feature that involves complex data migration. The development team estimates the work at 34 story points, but the sprint capacity is only 28 story points based on historical velocity. One developer suggests reducing quality checks to fit everything into the sprint, while another proposes splitting the migration into smaller, independently deliverable chunks. The product owner is concerned about delaying the feature launch. How should you proceed with sprint planning?
May 29, 2026
Your agile team has completed three sprints of a mobile application development project. During the retrospective, team members report that they consistently struggle to complete stories because dependencies on a third-party API team cause delays. The API team works in a different department and follows a waterfall approach with monthly release cycles. Several stories have been carried over to subsequent sprints, affecting the team's velocity. What should the product owner do to address this impediment?
May 29, 2026