PMP Practice Questions

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

You are managing a global hybrid project with agile development in North America and traditional implementation in Asia across a 12-hour time zone difference. A conflict has emerged where the Asian implementation team feels excluded from key decisions made during North American sprint planning, while the development team is frustrated by delayed responses to blockers. Cultural factors compound the issue: the Asian team is reluctant to speak up in virtual meetings dominated by North American voices, and the development team interprets silence as agreement. Project velocity has declined, and trust between teams is eroding. What approach BEST addresses these interconnected challenges?

August 21, 2026

Your organization is transitioning a traditional portfolio to hybrid delivery. You're managing a pilot project where a newly formed team combines waterfall veterans and agile practitioners. Three months in, the team has self-organized into methodology silos rather than integrating. The waterfall veterans have created extensive documentation and wait for complete requirements, while agile practitioners start building with minimal planning. Neither group attends the other's ceremonies, and integration points are being missed. The project is falling behind schedule, and the sponsor is questioning whether hybrid approaches work. What is the BEST strategy to transform this group into a cohesive team?

August 21, 2026

You are leading a product development project using a hybrid approach where design sprints inform traditional manufacturing phases. A highly skilled technical lead from the manufacturing team has begun undermining the design team's iterative decisions in stakeholder meetings, claiming 'real engineering requires upfront planning, not constant changes.' This individual's expertise is critical for production feasibility, but their behavior has caused two design team members to request transfers. The design team's psychological safety scores have dropped significantly, yet the technical lead's assessments have prevented three costly manufacturing errors. What should you do FIRST?

August 21, 2026

Your hybrid project team includes remote contractors working in iterative sprints and co-located employees handling regulatory compliance through sequential phases. You notice that the contractors consistently deliver on time, but employees are disengaged and missing milestones. During one-on-ones, several employees reveal they feel undervalued because contractors receive immediate feedback in daily standups while employees only get monthly status reviews. Performance metrics show contractor satisfaction at 85% while employee satisfaction has dropped to 45%. How should you address this disparity?

August 21, 2026

You are managing a hybrid project with both agile development teams and traditional infrastructure teams. During a retrospective, several agile team members express frustration that infrastructure dependencies are blocking their sprints. The infrastructure lead explains that their waterfall approach requires detailed specifications two months in advance, which conflicts with the agile team's adaptive planning. Team morale is declining, and velocity has dropped 30% over the last three sprints. What is the BEST approach to address this systemic conflict?

August 21, 2026

You are managing a defense contractor project with 30 team members working on classified deliverables. Three months into the project, a key architect who designed the overall solution structure has received a more lucrative offer from a competitor and will leave in two weeks. This architect's knowledge is essential for the next phase, and direct replacement is complicated by security clearance requirements that take 4-6 months. You have identified an internal candidate with relevant experience but who lacks the specific domain expertise. The project baseline includes detailed technical specifications, but much of the architect's design rationale exists only in email threads and meeting notes. Your sponsor is pressing you to maintain the current schedule. What is your best course of action?

August 20, 2026

You are managing a large construction project that has entered the execution phase. During a routine performance review, you discover that one of your site supervisors has been consistently inflating progress reports for the past three weeks, showing 85% completion when actual completion is closer to 65%. This supervisor is well-liked by the team, has 15 years of experience, and this is the first time you've encountered integrity issues with this individual. The misinformation has affected your earned value calculations and led you to reassign resources that were actually still needed. The project is visible to executive leadership, and you have a steering committee meeting in two days. What is the most appropriate course of action?

August 20, 2026

You are leading a pharmaceutical project to develop validation documentation for a new manufacturing process. The project team includes quality assurance specialists, process engineers, and regulatory affairs experts. During a critical review meeting, you observe that the QA specialists consistently dismiss input from the process engineers, citing regulatory concerns, while the engineers feel the QA team doesn't understand operational realities. This dynamic has resulted in rework cycles and is threatening the project's ability to meet regulatory submission deadlines. The organizational matrix structure gives you limited authority over these functional resources. How should you address this situation?

August 20, 2026

You are managing a government contract project following a predictive approach with strict scope, schedule, and budget constraints. During month 4 of the 12-month project, a key team member who holds critical institutional knowledge about legacy systems unexpectedly resigns. This team member was responsible for integrating the new system with three legacy platforms, and replacement hiring could take 6-8 weeks due to security clearance requirements. The integration work is scheduled to begin in 3 weeks. Your team suggests aggressively cross-training other members, but this would require pulling resources from their current critical path activities. What should you prioritize first?

August 20, 2026

You are managing a complex infrastructure project with a team of 45 members across three geographical locations. During the executing phase, you notice that two senior technical leads from different locations are consistently disagreeing on technical approaches during virtual meetings, causing delays in decision-making. The disagreements have begun to affect team morale, and other team members are starting to take sides. Both leads are highly skilled and their expertise is critical to project success. The project is currently on schedule but at risk of delays if this conflict continues. What is the most appropriate action to take?

August 20, 2026

A global technology company is executing a predictive project to standardize enterprise resource planning (ERP) systems across 47 subsidiaries in 23 countries, with a 42-month timeline and $310M budget. During month 28, while implementing in the European region, the company's board approves a significant corporate restructuring that will consolidate the 47 subsidiaries into 12 global business units organized by product line rather than geography. This restructuring will change reporting structures, business processes, financial consolidation requirements, and potentially the entire ERP architecture. The project has successfully implemented the system in 18 subsidiaries, with 12 more in various implementation stages. The CIO asks the project manager to assess the impact and recommend how to proceed. What should the project manager do first?

August 16, 2026

A manufacturing company is executing a predictive project to build a $220M production facility for automotive components in an emerging market. The project is month 21 of a 36-month timeline, with building construction complete and equipment installation beginning. Economic conditions in the target market have deteriorated significantly—currency devaluation of 35%, increased import tariffs on raw materials, and two major automotive customers have delayed their regional expansion plans by 2-3 years. The original business case projected ROI of 18% over 8 years based on specific production volumes and pricing. The CFO has requested an updated financial analysis and is considering project termination or conversion to a smaller-scale facility. Equipment purchases worth $78M are committed but not yet delivered. What should the project manager do?

August 16, 2026

A financial services company is executing a core banking system replacement project using a predictive methodology with a 30-month timeline and $95M budget. The project has completed detailed requirements, design, and procurement phases. During the development phase (month 16), the company acquires a smaller competitor that uses a different technology platform. The merger integration team proposes consolidating onto a single platform, which would either require abandoning the current project (wasting $42M invested) or forcing the acquired bank to migrate twice—first to their interim platform, then to the new system within 18 months. The PMO director asks the project manager to evaluate strategic options. Regulatory requirements mandate system consolidation within 24 months of acquisition closing. What analysis should the project manager prioritize?

August 16, 2026

A government infrastructure project worth $420M is in its execution phase using a predictive approach with a 5-year timeline. The project is building a regional transportation hub with multiple contractors. Three years into execution, a new administration takes office with different policy priorities and appoints a new agency director who questions the project's strategic alignment. The director requests a comprehensive benefits realization review before authorizing the next $150M funding tranche. Current earned value metrics show: SPI = 0.92, CPI = 0.88, with 58% of work completed. The project business case was approved under different economic assumptions, and inflation has increased costs by 14%. How should the project manager approach this situation?

August 16, 2026

A multinational pharmaceutical company is executing a predictive drug development project with a 4-year timeline and $180M budget. During year 2, a competitor receives FDA fast-track designation for a similar drug, potentially reducing the market window by 18 months. The project sponsor pressures the project manager to compress the schedule by overlapping clinical trial phases, which would violate regulatory protocols and risk patient safety. The governance board is split—some members prioritize speed-to-market while others emphasize compliance. Financial analysts project a $250M revenue loss if the competitor launches first. What should the project manager do first?

August 16, 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