PMP Practice Questions

You are managing a construction and technology project using a hybrid approach. Physical construction follows a critical path method schedule, while the building automation system development uses Kanban. The construction team has identified that they will complete the electrical rough-in two weeks ahead of schedule, which would allow the automation team to begin installation earlier than planned. However, the automation team's Kanban board shows they are currently focused on software configuration and have not yet started the installation work packages. What should you do?

July 29, 2026

Your hybrid project includes both traditional procurement activities managed through a stage-gate process and agile development work managed through Scrum. A critical vendor deliverable scheduled for the end of Stage 2 has been delayed by three weeks. The development team has planned the next two sprints based on receiving this deliverable at the originally scheduled time. The vendor cannot accelerate delivery, and the delay will impact six planned user stories. What should you do?

July 29, 2026

You are leading a product development project using a hybrid approach where regulatory compliance work follows a predictive model and feature development follows an agile model. During a retrospective, the agile team expresses frustration that they completed several features in the last sprint, but these features cannot be released to customers until compliance documentation is approved, which takes four weeks. The team feels their work is not creating value quickly enough. What is the best way to address this concern?

July 29, 2026

Your organization is implementing a new customer relationship management (CRM) system using a hybrid approach. The data migration and system configuration follow a waterfall methodology, while new feature development uses Scrum. After three sprints, the product owner reports that business stakeholders are confused about when they will see complete functionality because some features depend on data migration milestones that are tracked separately. Stakeholders are requesting a unified view of progress. How should you address this situation?

July 29, 2026

You are managing a digital transformation project using a hybrid approach. The planning team has completed traditional infrastructure work breakdown structures (WBS) while the software development team operates in two-week sprints. During sprint planning, the development team identifies dependencies on infrastructure components that are scheduled to be delivered in three months according to the WBS. The development team wants to begin user interface work now, but the infrastructure team insists on following the original schedule. What should you do first?

July 29, 2026

Your hybrid project is developing a medical device that requires FDA approval. The hardware development follows a stage-gate process with formal reviews, while the software uses an adaptive approach with continuous integration. The regulatory affairs team has raised concerns that the adaptive software approach lacks sufficient documentation and traceability for FDA submission. The software team argues that their automated testing and version control provide better traceability than traditional documentation. The regulatory deadline for submission is in four months, and both teams are at an impasse. Delays in resolving this could jeopardize the regulatory approval timeline. What should you prioritize?

July 27, 2026

You are leading a hybrid infrastructure modernization project with a $5M budget and 18-month timeline. The cloud migration work is being executed in two-week sprints using Scrum, while the network infrastructure upgrades follow a predictive schedule due to regulatory requirements and vendor dependencies. You've established a burn-up chart for the adaptive work and an earned value management system for the predictive work. At the 9-month mark, the cloud migration is progressing well with 60% of planned story points completed, but the network infrastructure shows a CPI of 0.78 and SPI of 0.85. The infrastructure delays are now blocking three upcoming cloud migration sprints. The sponsor asks for a realistic forecast of the final cost and completion date. What should you do?

July 27, 2026

You are managing a hybrid digital transformation project where the mobile application is developed using Kanban, the enterprise integration layer uses iterative development with monthly releases, and the legacy system upgrades follow a waterfall approach. Each component has separate teams with their own quality standards. During a recent production release, a critical defect was discovered that originated from miscommunication about data format expectations between the mobile team and integration team. The mobile team followed their Definition of Done which included unit testing, but the integration team assumed end-to-end testing would catch integration issues. This is the second integration defect in three months. What is the most effective long-term solution?

July 27, 2026

Your organization is executing a hybrid project to modernize its supply chain platform. The backend API development follows Scrum methodology, while hardware procurement and installation follow a predictive approach with fixed milestones tied to vendor contracts. You've established a cadence where API sprints are two weeks, and you conduct integrated planning every six weeks. During the third integrated planning session, the product owner requests prioritizing new API features that require hardware capabilities not included in the current procurement contract. The hardware lead indicates that modifying the contract will take 8-10 weeks and increase costs by 15%. The product owner argues these features are critical for competitive advantage. How should you proceed?

July 27, 2026

You are leading a hybrid project implementing a new customer relationship management (CRM) system. The infrastructure and data migration components are being executed using predictive approaches with detailed schedules, while the user interface customization is being developed iteratively with two-week sprints. During Sprint 3, the development team discovers that database schema changes required for a new UI feature will impact the data migration timeline, which is currently on the critical path. The infrastructure team needs three weeks to implement the schema changes, but this will delay the overall project completion by two weeks. What should you do first?

July 27, 2026

You are leading a project that combines agile development sprints with a traditional stage-gate approval process for major releases. The development team has completed all sprint work for the current release, but a quality gate review is scheduled for two weeks from now. The team is asking what they should work on next. What should you recommend?

July 22, 2026

Your project uses Scrum for software development and a waterfall approach for regulatory compliance activities. During sprint planning, the team identifies they need a compliance review completed before they can implement a new feature. The compliance review is scheduled for next month according to the predictive plan. What is the best way to handle this situation?

July 22, 2026

You are managing a hybrid project where the development team works in two-week sprints while the infrastructure team follows a predictive approach. The development team has completed their sprint and is ready to deploy, but the infrastructure team needs two more weeks to complete their planned activities. Stakeholders are asking when the feature will be available. What should you do first?

July 22, 2026

You are managing a project where the design phase follows a predictive approach with detailed upfront planning, but the implementation phase uses Scrum. The design phase has just completed, and you are transitioning to implementation. Several team members who worked on design are asking how they will track progress now. What should you explain to them?

July 22, 2026

Your hybrid project has a product backlog for agile work and a work breakdown structure (WBS) for predictive components. A new stakeholder requirement emerges that could impact both the agile and predictive portions of the project. The business value is clear, but implementation approach is uncertain. How should you handle adding this requirement?

July 22, 2026

An insurance company is executing a hybrid project to modernize their claims processing system. Infrastructure and security hardening follow a predictive approach with stage gates, while claims processing features are delivered in two-week sprints with regular customer demos. During a retrospective, the development team expresses frustration that they frequently wait for infrastructure approvals that delay their ability to deploy completed features. The infrastructure team explains their governance process requires formal change advisory board reviews that occur monthly. What is the best approach to address this impediment?

July 20, 2026

A retail company is implementing a hybrid project for a new inventory management system. The data migration follows a predictive schedule with specific cutover dates, while new features are developed using Kanban with continuous flow. A critical quality issue is discovered in the data migration test environment that could delay the cutover by six weeks. The development team using Kanban has been consistently delivering new features every week. Several stakeholders suggest accelerating feature delivery to compensate for the data migration delay. What should the project manager do?

July 20, 2026

A healthcare organization is delivering a patient management system using a hybrid approach. Regulatory compliance components follow a waterfall methodology, while clinical workflow features are developed iteratively based on user feedback. During a quarterly steering committee meeting, executives request a comprehensive status report showing progress across both work streams. The adaptive team measures velocity and completed story points, while the predictive team tracks earned value and milestone completion. How should the project manager present this information?

July 20, 2026

A manufacturing company is executing a hybrid project to implement a new production line. The engineering design follows a predictive approach with defined milestones, while the software automation team uses Scrum with three-week sprints. The engineering team has just completed their design phase two weeks ahead of schedule. The automation team's product owner wants to immediately begin working on advanced features that depend on the completed design, even though their current sprint has two weeks remaining and focuses on basic functionality. What should the project manager recommend?

July 20, 2026

A financial services company is implementing a new customer portal using a hybrid approach. The predictive portion involves infrastructure setup and regulatory compliance documentation, while the adaptive portion covers user interface development with two-week iterations. During sprint planning, the infrastructure team reports they need three additional weeks to complete security certifications before the development team can begin integration testing. The project manager is concerned about the impact on the overall timeline. What should the project manager do first?

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