What could have caused confusion during a Sprint Review when demonstrating previous increments?

The choice indicating that developers not adhering to the Definition of Done can lead to confusion during a Sprint Review is insightful because the Definition of Done serves as a clear agreement within the team about what constitutes a complete, potentially shippable increment. If developers fail to adhere to this definition, it results in increments that may not meet the expected quality or functionality. This can create uncertainty for stakeholders when they view and evaluate the work presented, as the increment may contain unfinished or subpar features, leading to misconceptions about the team's progress and the viability of the product.

When the Definition of Done is not rigorously followed, stakeholders may leave the Sprint Review with unclear or negative impressions about the overall project status and the team’s performance. This detracts from the purpose of the Sprint Review, which is to transparently showcase completed work, gather feedback, and adapt the product backlog accordingly. Therefore, adherence to the Definition of Done is crucial for avoiding confusion and ensuring that stakeholders have a clear, accurate understanding of the current state of the product.