Handling Bugs Found in a Previous Increment
When a bug is discovered in software that was delivered in a previous Increment, it’s important to handle it in a way that aligns with Scrum principles and maintains the integrity of the current Sprint’s work.
Exam Question
While changing software, you find a bug delivered in a previous Increment. What should you do?
(choose the best answer)
A. Revise the tests so that the bug no longer appears on the bug report.
B. Talk to the Product Owner about what steps to take.
C. Set aside the Sprint Goal until the bug is fixed.
D. Stub out the code that caused the bug so it no longer occurs.
Correct Answer
B. Talk to the Product Owner about what steps to take.
Explanation
Correct Answer
B. Talk to the Product Owner about what steps to take:
When a bug is found in a previously delivered Increment, the first step should be to consult with the Product Owner. The Product Owner is responsible for managing the Product Backlog and making decisions about the priority of work items, including whether fixing the bug should take precedence over the current Sprint Goal or be addressed in a future Sprint. This ensures that the decision aligns with the overall product strategy and value delivery.
Why the Other Options Are Less Appropriate
A. Revise the tests so that the bug no longer appears on the bug report:
This approach is not appropriate because it hides the problem rather than addressing it. Revising tests to ignore the bug is not a responsible or effective way to handle software quality issues.
C. Set aside the Sprint Goal until the bug is fixed:
While fixing bugs is important, abandoning the Sprint Goal is not advisable without a proper discussion with the Product Owner. The Sprint Goal represents a commitment, and any decision to change it should involve the Product Owner.
D. Stub out the code that caused the bug so it no longer occurs:
Stubbing out the code to prevent the bug from occurring is a workaround rather than a fix. It doesn’t address the underlying issue and could introduce further problems down the line. Properly fixing the bug is the preferred approach, and this decision should involve the Product Owner.
Relevance to the PSD Exam
Understanding how to handle bugs found in previous Increments is crucial for the PSD exam. It emphasizes the importance of communication with the Product Owner and making decisions that align with the product’s priorities and Sprint Goals.
Key Takeaways
- Communication with the Product Owner is essential when a bug is found in a previous Increment. They will help prioritize the fix and decide how it fits within the current Sprint.
- Avoid workarounds like revising tests or stubbing out code, as these do not address the underlying issue.
- Maintaining the Sprint Goal is important, and any decision to alter it should involve the Product Owner.
Conclusion
When a bug is discovered in a previous Increment, the best course of action is to discuss the issue with the Product Owner. This ensures that the bug is prioritized appropriately and handled in a way that aligns with the product’s overall goals and current Sprint commitments. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.
