Undone work on the increment?
Let's take a look to this statement at 3.2. What is “undone” work?
"Work on the Increment that hasn’t achieved the quality standards outlined in the Definition of Done is work that is not yet “done.”"
If there is undone work on the increment that's not an increment. Isn't it?
I should sugest rewrite it as
"Work on the Sprint that hasn’t achieved the quality standards outlined in the Definition of Done is work that is not yet “done.”"
The Sprint is only a container. Work cannot be done on or to the Sprint.
When working, the team modifies a previous Increment to make changes. A potential Increment remains in an undone state. When a Product Backlog Item meets the Definition of Done, a new Increment is created, which can potentially be delivered to stakeholders for use.
If there is undone work on the increment that's not an increment. Isn't it?
The Definition of Done is a commitment associated with the Increment. If work has been undertaken on the Increment and the commitment not yet satisfied, the outstanding work ought to be accounted for on the Product Backlog.
The Sprint that contributed to the deficit is irrelevant. It might have been the current one, or a previous one, or a Sprint conducted at some point by another team.
Thanks guys.
So, let's say that if we have work completed that meets DoD standards, then we have a new increment, regardless of whether it constitutes all or part of a PBI selected for the sprint or SBI.