What is a Proper Agile Iteration (Sprint)? Part 3: Done Done *

A developer marking coding as complete is a long way from being truly 'Done, Done' in Agile.

I share my view of “Proper Agile Iteration (Sprint)” in this series:

• Part 1: User Story *

• Part 2: Testing and Coding *

• Part 3: Done Done *

• Part 4: Continuous Testing (upcoming)

• Part 5: Showcase (upcoming)

• Part 6: ‘Production’ Deployment (upcoming)

• Part 7: Sustained Pace (upcoming)

'Done, Done’ is an agile term:

Done Done
“We’re done when we’re production-ready” — The Art of Agile Development book

The first 'Done,' by convention, indicates that a developer believes the implementation of the user story is satisfactory based on their own testing. However, it still needs to be verified by another person.

Verified by Business Analyst/Tester Does not meet the second “Done”

The second 'Done' is commonly seen as a business analyst or tester verifying the user story based on its acceptance criteria (typically written on the back of the card).

This verification can be manual or automated. If testing is conducted professionally, many so-called ‘agile’ teams consider the work—whether a new feature or bug fix—complete. But in reality, it is NOT.