Why change the done state? | Insight

Why change the done state?

Many charts depend on the done state to display how the team is progressing.

A common example of this is when another team is responsible for QA. In this kind of process, the burn down chart becomes less representative of reality as it will flatline until the QA team marks the story as accepted.

Here is what it would look like when tracking it by accepted stories:

To avoid this situation, some teams prefer to track a story until it's delivered or finished instead of accepted because that's the part they actually control (here is how).

Here is what the same burn down chart would look like if it was tracked by finished as the done state:


The latter is a much better indicator of how the team is progressing in the iteration since it doesn't include their external dependence on the QA team.

Leran more on how the done state can lead to better software and increased productivity.