A project manager is leading a project to develop a new mobile application. The team has identified a critical design flaw after the initial prototype was developed, which requires a significant rework of the user interface (UI) and backend integration. The project is using an adaptive (agile) approach. What should the project manager do NEXT?
- AInstruct the development team to immediately begin the rework to minimize delays.
- BAdd the necessary rework tasks to the product backlog and re-prioritize with the product owner.
- CSubmit a formal change request to the change control board to approve the rework.
- DEscalate the issue to the project sponsor for a decision on whether to proceed with the rework.
Show answer & explanationAnswer & explanation
Correct answer: B. Add the necessary rework tasks to the product backlog and re-prioritize with the product owner.
In an adaptive (agile) environment, significant changes, even those due to flaws, are managed through the product backlog. The product owner, in collaboration with the team and stakeholders, is responsible for prioritizing items in the backlog, including rework, based on value and urgency. This allows for flexibility without formal change control board processes typical of predictive approaches.
Why the other options are wrong
- A. Beginning rework immediately without proper prioritization and stakeholder alignment can lead to wasted effort or addressing the wrong problem first.
- C. Formal change requests and CCBs are more typical of predictive (waterfall) projects, not adaptive ones for internal adjustments.
- D. Escalation to the sponsor is premature; the agile process provides internal mechanisms for managing such changes through the product owner.
Product Backlog Management (Agile)
The continuous process of adding, refining, and prioritizing items (features, defects, technical debt, or rework) in the product backlog to maximize the value delivered by the agile team.
- Product Owner is primarily responsible.
- Items are prioritized based on value, risk, and dependencies.
- Serves as the single source of work for the development team.
Memory trick: Flaw found? 'BACKLOG' it and 'PRIORITIZE'!