PMP Practice Questions

You are managing a product development project using a hybrid approach: market research and regulatory approval follow a stage-gate process, while the product design team works in 2-week sprints. Gate 3 approval requires completed safety testing documentation that depends on design specifications from Sprint 8. Currently in Sprint 5, the design team wants to pivot based on user feedback that suggests a significantly different approach with better market potential but would require new safety protocols. The gate review is scheduled in 8 weeks, and delay would miss a critical industry conference launch window. The product owner supports the pivot for competitive advantage. What should you prioritize?

July 7, 2026

Your organization is executing a hybrid project to implement an enterprise system. The data migration and infrastructure components use a predictive approach with detailed WBS and Gantt charts, while business process customization follows Scrum. During the fourth sprint, the team discovers that the assumed data structure from the migration plan is incompatible with a critical business process they're configuring. Resolving this requires changes to both the migration approach and already-completed sprint work. The infrastructure team resists changes to their plan, citing baseline control processes. What is the best way to proceed?

July 7, 2026

You are leading a transformation project using a hybrid approach where infrastructure deployment follows a predictive model and application features are developed iteratively. The project baseline includes a fixed budget of $2M and a 12-month timeline. After 6 months and $1.1M spent, earned value analysis shows CPI of 0.91 and SPI of 0.88. Meanwhile, the adaptive track has delivered 45% of planned story points with high stakeholder satisfaction. The sponsor questions whether the project is failing and considers cancellation. How should you respond?

July 7, 2026

Your hybrid project uses time-boxed iterations for software development and a phase-gate approach for hardware components. During iteration review, the team demonstrates completed software features, but stakeholders from the hardware division express concern that integration testing cannot occur until their component passes the design gate in 6 weeks. The software features cannot be released independently and are accumulating as technical inventory. Velocity metrics show the team is productive, but no value is being delivered to customers. What is the most appropriate action?

July 7, 2026

You are managing a hybrid project where regulatory compliance features are being developed using a predictive approach while customer-facing enhancements follow Scrum. During sprint planning, the development team identifies dependencies between a compliance module (scheduled for completion in 3 months per the WBS) and a user interface feature planned for the current sprint. The compliance module is on the critical path and any acceleration would require additional resources. The product owner insists the UI feature delivers significant customer value and should not be delayed. What should you do first?

July 7, 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

You are leading a product development project using a hybrid approach where design and development follow Scrum, but manufacturing and supply chain operate in predictive phases. A key team member from manufacturing, who has 20 years of experience, consistently questions agile practices in cross-functional meetings, stating 'this would never work in the real world' and 'we tried this before and it failed.' This is creating doubt among other team members and reducing engagement in collaborative planning sessions. The manufacturing manager confirms this person's technical expertise is critical to project success. What is the most appropriate way to address this?

July 7, 2026

Your hybrid project team includes employees and contractors from a vendor organization. The vendor's contract specifies fixed deliverables and milestones, while your internal team operates using agile sprints with flexible scope. During a sprint review, stakeholders request significant changes that would benefit the product but would require substantial rework from the vendor team. The vendor project manager states they cannot accommodate changes without a contract modification and additional payment. Your internal team is frustrated by the vendor's 'inflexibility.' What should you do?

July 7, 2026

You are managing a hybrid transformation project where half the team is experienced with agile practices and half has only worked in traditional environments. During the first iteration planning session, the traditional team members remain silent while the agile-experienced members dominate the discussion. Later, a traditionally-trained business analyst tells you privately that they feel their expertise in requirements documentation is no longer valued. The project requires both detailed requirements for regulatory purposes and iterative development. How should you address this situation?

July 7, 2026

Your hybrid project has a distributed team across three time zones. The agile software development team conducts daily standups, while the regulatory compliance team works in traditional phases with monthly reviews. You notice that collaboration between these groups is minimal, causing delays when compliance requirements impact sprint deliverables. The compliance lead insists their work cannot be broken into smaller increments, while the development team lead complains about last-minute compliance changes. What is the best approach to improve collaboration?

July 7, 2026

You are leading a hybrid project where the development team works in two-week sprints while the infrastructure team follows a waterfall approach with phase gates. During sprint planning, a senior developer publicly criticizes a junior team member's previous work, causing visible discomfort. The junior member becomes withdrawn for the remainder of the meeting. Several team members later approach you expressing concern about the negative team dynamics. What should you do first to address this situation?

July 7, 2026

You are managing a product development project using a predictive approach. The project management plan has been approved and execution has begun. During a team meeting, you realize that several team members are unclear about their specific responsibilities and who has decision-making authority for various project activities. This confusion is beginning to cause delays. What document should you reference or update to clarify these roles and responsibilities?

July 2, 2026

You are leading a predictive infrastructure project that is currently in the executing phase. A stakeholder who was not involved in initial planning requests a significant change to the project scope that would add new deliverables. The stakeholder insists the change is critical and wants it implemented immediately. What is the most appropriate action to take?

July 2, 2026

You are managing a manufacturing project to develop a new product line. During the execution phase, one of your team members discovers that a delivered component does not meet the specifications documented in the project requirements. The supplier claims the component meets industry standards, but it clearly does not match what was agreed upon in the procurement contract. What should be your first step?

July 2, 2026

You are planning a software implementation project for a financial services company. The project sponsor has approved a budget of $500,000. During cost planning, you need to establish a performance measurement baseline that will be used to monitor and control project costs throughout execution. The baseline should integrate scope, schedule, and cost to enable earned value management. What should you create?

July 2, 2026

You are managing a construction project to build a new office building. During the planning phase, you need to determine the total project duration by analyzing the sequence of activities and their dependencies. You have identified all activities, estimated their durations, and mapped out their logical relationships. What technique should you use to calculate the longest path through the project and identify the minimum project duration?

July 2, 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