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.
50 questions found · page 1 of 2
Your agile team is building a healthcare platform that must comply with HIPAA regulations. The compliance officer insists on reviewing and approving all designs before development begins and all code before deployment, which creates a bottleneck taking 5-7 days per review. The team's sprint cycle is two weeks, and this delay means most stories cannot be completed within a sprint. The compliance officer is unwilling to attend daily standups or sprint ceremonies, stating they are too busy. Team morale is declining as they cannot meet sprint goals. What is the MOST effective approach to resolve this situation?
August 24, 2026
Your agile team has been working on a financial services application for three sprints. During the sprint review, the product owner asks the team to demonstrate a complex regulatory reporting feature that was not part of the sprint backlog. The team lead explains they focused on the agreed sprint goal instead. The product owner becomes frustrated, stating this feature is critical for an upcoming audit and should have been obvious to include. Stakeholders at the meeting appear concerned about the team's ability to deliver. What should the Scrum Master do to address this situation?
August 24, 2026
You are leading a distributed agile team working on an IoT platform across three time zones. The team uses Kanban with WIP limits, and throughput has been consistent at 12 items per week. Recently, a major enterprise client requested a committed delivery date for a specific feature set, which your sales team communicated would take four weeks. The product owner asks you to guarantee this timeline and wants daily status reports to track progress. Your team has historically avoided commitments because of the variability in item complexity. How should you respond to this request while maintaining agile principles?
August 24, 2026
An agile team is delivering a customer-facing mobile application using two-week sprints. After six sprints, velocity has been stable at 40 story points per sprint, but customer satisfaction scores are declining. Analysis shows that while features are being delivered on schedule, they often require significant rework in subsequent sprints after user feedback. The product owner has been accepting all stories that meet the acceptance criteria at sprint reviews. Technical debt is accumulating, and the team's Definition of Done includes unit testing and code review but no user validation. What is the BEST approach to improve customer satisfaction?
August 24, 2026
An agile team working on a cloud migration project has been using story points for estimation with planning poker. After 10 sprints, a new senior developer joins who strongly advocates for switching to ideal hours instead of story points, arguing that hours are more precise and easier for stakeholders to understand. The team is divided—some members agree with the new developer, while others want to keep story points because their historical velocity data would become irrelevant. The upcoming sprint planning is in two days, and the product owner is concerned about any changes that might impact the team's predictability during a critical release cycle. What should you do?
August 24, 2026
Your agile team is developing a mobile healthcare application in a regulated environment. During sprint planning for sprint 8, the product owner presents user stories for a new patient data-sharing feature. The team identifies that implementing this feature requires integrating with a legacy hospital system that has unreliable APIs and poor documentation. Past experience shows that such integrations typically reveal unknown dependencies mid-sprint. The product owner insists this feature is critical for a partnership announcement in four sprints and must begin now. The team is concerned about committing to a sprint goal they may not achieve. What approach best balances the business urgency with empirical process control?
August 4, 2026
You are coaching an agile team that has achieved high performance, consistently delivering 55-60 story points per sprint with minimal defects. The organization's PMO has mandated that all teams adopt a new estimation approach using ideal hours instead of story points, claiming this will enable better cross-team resource planning and executive reporting. Your team objects strongly, arguing that story points reflect their shared understanding and that converting to hours will reduce their estimation accuracy. The PMO has set a deadline of two sprints to transition. Senior management supports the PMO initiative as part of portfolio-level standardization. What should you do?
August 4, 2026
Your product team is in sprint 6 of developing an AI-powered analytics platform. The product backlog contains 180 stories, and the product owner has been prioritizing based on business value scoring. During backlog refinement, the technical lead warns that continuing to build features on the current data architecture will create massive refactoring work later, potentially requiring 4-6 sprints to address. However, stakeholders are eager to see new analytics capabilities demonstrated at an industry conference in five sprints. The technical lead proposes dedicating the next two sprints entirely to architectural improvements with no visible features. How should you guide the product owner's decision?
August 4, 2026
You are leading an agile transformation for a distributed team building a customer portal. After three sprints, you notice that the team's velocity has dropped from 45 to 28 story points, and sprint goals are consistently not met. During daily standups, team members report blockers related to waiting for architectural decisions from a centralized enterprise architecture group that reviews designs every two weeks. The product owner is frustrated with slow progress and wants to add more developers. Team morale is declining as members feel they cannot control their outcomes. What is the most effective approach to restore the team's ability to deliver value?
August 4, 2026
Your agile team has been delivering increments for a regulatory compliance product over the past four sprints. During the sprint review, the compliance officer raises concerns that while individual features work well, the product lacks end-to-end workflow validation required for regulatory approval. The product owner argues that all acceptance criteria were met and signed off. Stakeholders are now questioning whether the product will pass the mandatory audit in two sprints. The team has velocity data showing consistent delivery, but no integrated compliance testing has been performed. What should you do first to address this situation?
August 4, 2026
During sprint planning, your cross-functional agile team is struggling with significant disagreement about story point estimates. Your senior architect insists a complex integration story is 5 points based on his experience, while two developers argue it's at least 13 points because they'll be doing the actual implementation and foresee multiple technical challenges. The product owner is pressuring for the lower estimate to fit more stories in the sprint. The tension is escalating, with team members becoming defensive and the meeting has already run 30 minutes over. How should you handle this situation?
August 3, 2026
You're managing an agile project for a healthcare application where the development team has been consistently high-performing with a velocity of 45-50 points per sprint. During the current sprint, you discover that two team members, both senior developers, have been involved in a personal conflict that has been escalating over the past month. The conflict began with disagreement over architectural decisions but has become personal, with both individuals now refusing to pair program together and making passive-aggressive comments in team channels. Other team members are starting to take sides, and you notice work items requiring both developers' expertise are being delayed. In yesterday's standup, one developer made a sarcastic comment about the other's code quality in front of the entire team. What should you do?
August 3, 2026
Your distributed agile team spans three time zones (US West Coast, US East Coast, and India). Team members in India have been increasingly quiet during sprint ceremonies and retrospectives. Your scrum master in India privately shares that the Indian team members feel their opinions aren't valued because decisions seem to be made during US hours, and they're frustrated with being woken up for 'urgent' calls at 2 AM their time. Meanwhile, US team members complain about slow response times and feel the India team isn't collaborative. Team morale is declining and your last sprint failed to meet its goals. What should be your priority action?
August 3, 2026
You are coaching a newly formed agile team that includes Maria, a product owner who came from a traditional project management background. She has been writing detailed requirement documents (15-20 pages) for each feature, specifying exact UI layouts, error messages, and technical implementation approaches before bringing them to the team. The team is overwhelmed and sprint planning takes 6-8 hours because they must read through extensive documentation. Developers are becoming disengaged, and one told you privately that 'we're just code monkeys implementing Maria's designs.' Maria believes she's helping the team by being thorough. What is your best approach?
August 3, 2026
You are leading an agile transformation for a traditional organization. Your team of 9 members includes 3 developers who consistently resist attending daily standups, claiming they are 'a waste of time' and that they work better independently. These developers are highly skilled and deliver quality code, but their absence is creating information silos and frustrating other team members who rely on their updates. Team velocity has dropped 15% over the last two sprints, and you notice integration issues emerging late in sprints. What should you do first?
August 3, 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
Your agile team is developing a cloud-based platform for a healthcare provider. Six months into the project, a major technology vendor announces end-of-support for a core component your architecture depends on, effective in 18 months. Replacing this component requires significant architectural changes. Simultaneously, your organization is negotiating a potential merger with another healthcare provider that uses a completely different technology stack. The Product Owner wants to continue building features on the current architecture. The enterprise architect recommends pausing feature development to address technical sustainability. Several team members suggest waiting for merger clarity before making major technical decisions. What should you recommend?
July 7, 2026
Your organization is using agile methodologies for a digital transformation initiative spanning multiple business units. During a governance review, the PMO director presents data showing that while agile teams report 85% sprint completion rates, the overall program is only delivering 40% of the business outcomes defined in the original business case approved 18 months ago. The PMO recommends implementing stage gates and more rigorous upfront planning. The agile coaches argue the business case was based on outdated assumptions and that teams are delivering valuable working software every sprint. The CFO wants to understand why the significant investment isn't producing expected business results. How should you address this situation?
July 7, 2026
Your organization operates in a highly competitive market where a major competitor just announced a disruptive product launch in 6 months. Your agile team is currently working on a 12-month product roadmap with different features. The executive team wants to immediately shift focus to competitive features, but your Product Owner believes the current roadmap addresses more fundamental customer needs that will provide sustainable differentiation. Your team's velocity suggests they cannot deliver both sets of features within 6 months. Market analysis shows the competitor's announcement has already impacted your pre-orders by 30%. What is the best course of action?
July 7, 2026
You are leading an agile transformation for a manufacturing company that has traditionally used waterfall approaches. The executive sponsor allocated $2M for a new product line with expected ROI within 18 months. After three quarters, your agile teams have delivered multiple increments with strong customer feedback, but the CFO reports the project has consumed $1.8M with revenue projections now showing a 24-month ROI timeline. The teams argue they are delivering valuable features and the extended timeline is due to market conditions, not delivery issues. Senior management is considering canceling the initiative. How should you respond?
July 7, 2026
Your agile team is developing a mobile application for a financial services company. During Sprint 3, new government regulations are announced requiring additional security controls that will significantly change the product architecture. The Product Owner wants to continue with the current sprint commitments while addressing the regulatory changes in future sprints. The compliance officer insists all work must stop until the new requirements are incorporated. The team is concerned about technical debt if they don't refactor now. What should you do as the Scrum Master?
July 7, 2026