PMP Practice: Determine appropriate feedback approach

This scenario tests the scrum master's ability to balance immediate delivery pressure with sustainable team development in an agile environment. The correct approach is to facilitate collaborative problem-solving that honors both legitimate concerns rather than making a unilateral decision or forcing a binary choice. By bringing the team together to examine actual data about technical debt impact and explore creative solutions, Diego enables the team to self-organize around the constraint. The key insight is that mentoring and delivery are not mutually exclusive — the team might identify approaches like timeboxed pairing sessions, focused code review workshops during existing ceremonies, or strategic task assignment that builds junior skills while maintaining velocity. This approach respects the team's expertise, maintains transparency about tradeoffs, and builds team ownership of both quality and delivery commitments. It also recognizes that in agile environments, the team collectively determines how to meet sprint goals, and the scrum master's role is to facilitate that decision-making process rather than impose solutions. The scenario's closing facts — that improvement is happening but rework is real, and that scope is already minimal — indicate that the answer must acknowledge both concerns rather than dismissing either.

**Why not A:** Escalating to the product owner and publisher removes the decision from the team and treats it as a business-only question. The tradeoff involves both technical sustainability and business delivery, and the team has the context to explore creative solutions that might address both concerns without requiring external arbitration.

**Why not B:** Siding with the current pace and deferring mentoring until after launch ignores Kenji's legitimate concern that technical debt from junior code quality will slow future sprints. With the product owner confirming this is minimum viable scope, any velocity degradation from accumulated rework could threaten the remaining sprints before launch.

**Why not D:** Reducing the sprint commitment by 20% unilaterally to create mentoring time oversteps the scrum master's role. The team should collectively determine how to balance their commitments, and reducing committed story points when the product owner has stated the current scope is the minimum viable product may jeopardize the launch without exploring alternatives.