According to the PMBOK Guide, backlog grooming (also known as backlog refinement) is the process of reviewing, updating, and prioritizing the product backlog items to ensure that the product backlog is ready for the next sprint1. Backlog grooming is an ongoing activity that involves collaboration between the product owner, the development team, and the project manager (or scrum master). Backlog grooming helps to clarify the requirements, remove ambiguity, identify dependencies, estimate effort, and align the product backlog with the product vision and the customer needs2.
In this question, the project manager is faced with a problem that the product owner has uncovered a number of issues that they would like to be addressed before providing approval for the software built to date. These issues may indicate that the product owner is not satisfied with the quality, functionality, or usability of the software, or that the software does not meet the acceptance criteria or the customer expectations. The project manager should approach this problem by planning to address the issues through backlog grooming and incorporating them into the next sprint. This way, the project manager can ensure that the issues are properly documented, analyzed, and prioritized, and that the development team can work on them in the next iteration. This will also help to maintain the agile principles of delivering value, satisfying the customer, and embracing change3.
The other options are not the best ways to approach this problem. Referring the product owner to the change management plan, then escalating to the steering committee is not appropriate for an agile project, as it implies a rigid and formal process that may not be responsive to the customer feedback and the changing requirements. Referring the product owner to the signed business requirement document and explaining that the current plan cannot facilitate these changes is not helpful, as it may create conflict and dissatisfaction with the product owner, and it may also indicate that the project manager is not following the agile value of responding to change over following a plan3. Telling the product owner the issues will be addressed in the second version of the software is not acceptable, as it may delay the delivery of value, compromise the quality of the product, and lose the trust of the product owner.
References: 1: PMBOK Guide, 6th edition, p. 179 2: Backlog Grooming: How to Do It and Why It Matters, ProjectManager.com, July 2020, 1 3: Manifesto for Agile Software Development, Agile Alliance, 2001, 2
Submit