PMP Guide — Empowering Project Managers
ProcessAgileHardECO: Process Task 3.16

Your agile team has been delivering features every two weeks for six months. During the latest sprint review, a key stakeholder expresses frustration that the product increment doesn't align with their vision, despite approving stories throughout development. The product owner admits they've been accepting stories based on technical completion rather than business value validation. Technical debt has accumulated, and the team's velocity has dropped 30% over the last three sprints. What should you do first to address this systemic issue?

← All questions
📖

Study this topic

WBS Work Breakdown Structure: Proven Best Practices

Master the essential techniques for creating effective Work Breakdown Structures that drive project success and align wi

More Process Questions

View all →
1
MediumPredictive

Your manufacturing equipment upgrade project is in the executing phase. A key vendor has submitted deliverables for the third milestone, but during the inspection process, your quality assurance team identifies that 15% of the components do not meet the specifications outlined in the procurement contract. The vendor claims the specifications were ambiguous and requests additional payment to remake the components. This is causing a potential two-week delay. What is the BEST course of action?

2
MediumPredictive

You are managing a construction project with a fixed budget of $2.5 million and a 14-month timeline. During month 6, you conduct an earned value analysis and discover that the Cost Performance Index (CPI) is 0.85 and the Schedule Performance Index (SPI) is 0.92. The project sponsor asks you to forecast the final project cost and determine what actions are needed. Using the current performance trends, what is the most appropriate estimate at completion (EAC) if you believe current variances are atypical and future work will be performed at the planned rate?

3
MediumHybrid

You are leading a regulatory compliance project using a hybrid approach where legal requirements are managed predictively with sequential gate approvals, while technical implementation uses iterative sprints. After three sprints, the compliance team reviews the working software and identifies that two implemented features may not fully satisfy regulatory requirements. The development team argues that requirements were ambiguous and their interpretation was reasonable. The next compliance gate is in two weeks. What is the best course of action?