PMP Practice Questions

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 team is developing a mobile banking application for a financial services company. During Sprint 3, new government regulations are announced that require additional security features and data encryption standards. The product owner wants to continue with the current sprint plan, arguing that regulatory changes can be addressed in future sprints. The compliance officer insists these changes must be implemented immediately to avoid potential legal issues. What should the Scrum Master recommend?

July 30, 2026

You are leading an agile transformation for a product development team in a manufacturing company. The organization has a strong command-and-control culture with rigid hierarchies. Middle managers are resisting the change, concerned about losing authority as teams become self-organizing. Team members are enthusiastic but uncertain about their new responsibilities. Senior leadership supports the transformation but expects quick results. How should you proceed to ensure sustainable adoption?

July 30, 2026

Your agile team is developing a customer relationship management (CRM) system. A major competitor has just launched a similar product with innovative AI-powered features that are generating significant market buzz. Your sales team is pressuring the product owner to immediately pivot and incorporate similar AI capabilities, even though this was not part of the original product vision. The development team has concerns about technical feasibility within the current timeline. What should the product owner do first?

July 30, 2026

An agile software development team is working for a client in a highly regulated healthcare industry. The team has been successfully delivering increments every two weeks, but the client's compliance department now requires a formal risk assessment and approval process before each release to production. This approval process typically takes 5-7 business days. The team's velocity is being impacted, and stakeholders are frustrated with the deployment delays. What is the best approach to address this situation?

July 30, 2026

Your organization is launching an agile project to develop a new e-commerce platform in an emerging market with significant economic and political uncertainty. During sprint planning for Sprint 4, news breaks about potential new import tariffs that could affect the cost structure and viability of the business model. The development team wants to continue building planned features, while the finance team suggests pausing development until the regulatory situation becomes clearer. What should the project leader recommend?

July 30, 2026

Your agile team has consistently achieved their sprint goals for the past four sprints. However, during a stakeholder demo, you receive feedback that while features are being delivered, they don't seem to align well with user needs. The product owner has been making prioritization decisions independently without consulting users or stakeholders between sprint reviews. Team morale is starting to decline as developers feel their hard work isn't creating real value. What should you do as the agile project leader?

July 27, 2026

Your agile team has a new member, Sarah, who joined two weeks ago. Sarah has strong technical skills but comes from a traditional waterfall background. During the current sprint, you notice Sarah working in isolation, not updating the task board, and not asking for help despite her story being blocked. In the standup, she reports 'everything is fine' even though you can see she's struggling. Other team members have offered help, but she politely declines. What is the most effective way to help Sarah adapt to the agile team environment?

July 27, 2026

During sprint planning, your development team commits to 45 story points based on historical velocity. However, your product owner insists they must complete 60 story points this sprint because of a commitment made to a key stakeholder. The product owner argues that the team 'just needs to work harder' and threatens to escalate to senior management if the team doesn't comply. The team looks to you, the Scrum Master, for guidance. How should you respond?

July 27, 2026

Your agile team is distributed across three time zones. During daily standups, team members in the earliest time zone often seem disengaged and provide minimal updates. You've discovered these team members start their workday two hours before the scheduled standup and lose momentum waiting for the meeting. The team agreed to the current time as a compromise. Productivity metrics show these early-timezone members have 20% lower story completion rates than others. What is the best approach to address this situation?

July 27, 2026

You are leading an agile team that has been working together for three sprints. During the latest retrospective, two senior developers dominate the discussion while three junior team members remain silent. You notice the junior members attempted to speak but were interrupted. The retrospective facilitator did not intervene. Team velocity has plateaued, and you suspect untapped ideas from quieter members could help. What should you do to improve team engagement in future retrospectives?

July 27, 2026

Your agile team has two members who have different communication styles that are creating tension. One team member prefers detailed written documentation and asynchronous communication, while the other prefers quick verbal discussions and face-to-face interaction. Their different approaches have led to misunderstandings about requirements and growing frustration between them. Other team members are starting to take sides. What should you do first?

July 22, 2026

During sprint planning, your development team commits to 25 story points based on their historical velocity. However, the product owner insists that 35 story points must be completed this sprint to meet a critical market window. The product owner escalates to senior management, who pressure you to have the team commit to the higher number. The team is frustrated and feels their professional judgment is being dismissed. What is the best way to handle this situation?

July 22, 2026

Your agile team includes a highly skilled developer who consistently completes stories faster than estimated. However, other team members have privately expressed concern that this developer rarely participates in pair programming sessions, doesn't share knowledge during daily standups, and works in isolation. While individual productivity is high, the team's overall capability isn't improving, and there's a growing knowledge silo. How should you address this situation?

July 22, 2026

You are leading an agile project team that has been working together for three sprints. During the latest retrospective, several team members express frustration that decisions are taking too long because everyone wants to provide input on every issue. The team's velocity has decreased by 20% over the past two sprints, and sprint goals are being missed. Team morale is declining as members feel meetings are consuming too much productive time. What should you do to address this situation?

July 22, 2026

You are coaching a newly formed agile team for a financial services project. Three team members have deep expertise in the legacy systems but no agile experience, while two members are experienced agile practitioners but new to the domain. During the first sprint, you notice the legacy experts are reluctant to break work into small increments and prefer to complete entire features before showing anything. The agile practitioners are frustrated by this approach. The team is struggling to complete even simple stories. How should you address this?

July 22, 2026