A newly formed Agile team is struggling with frequent changes to requirements mid-Sprint, leading to incomplete work and missed Sprint Goals. The Product Owner is actively engaged but often brings new insights from stakeholders. Which Agile principle is most directly being violated, and what should be done?
- ACustomer collaboration over contract negotiation; the Product Owner should sign off on requirements earlier.
- BResponding to change over following a plan; the team should embrace all changes immediately.
- CWorking software over comprehensive documentation; the team should protect the Sprint Goal from scope creep.
- DIndividuals and interactions over processes and tools; the team needs better communication tools.
Show answer & explanationAnswer & explanation
Correct answer: C. Working software over comprehensive documentation; the team should protect the Sprint Goal from scope creep.
While Agile values responding to change, it also emphasizes sustainable pace and protecting the Sprint Goal. Frequent mid-Sprint changes indicate a violation of the principle of delivering 'working software over comprehensive documentation' if those changes undermine the ability to produce a 'Done' increment. The team needs to protect the Sprint Goal from scope creep by having a clear definition of 'Done' and negotiating changes for future Sprints.
Why the other options are wrong
- A. Customer collaboration is good, but signing off earlier doesn't address mid-Sprint changes; Agile prefers continuous feedback.
- B. Responding to change is an Agile value, but it doesn't mean accepting all changes mid-Sprint without jeopardizing the Sprint Goal. This option promotes an unsustainable approach.
- D. While communication is important, the core issue is scope stability within a Sprint, not just tool deficiency.
Protecting the Sprint Goal
A core Agile practice where the Development Team commits to achieving a specific Sprint Goal, and changes that threaten this goal are carefully managed, often deferred to future Sprints.
- Ensures focus and predictability within a Sprint.
- Prevents scope creep from undermining 'Done' increments.
- Requires negotiation and collaboration with the Product Owner regarding changes.
Memory trick: Agile values guide us, but the Sprint Goal is our compass; protect it to deliver true value.