I came across this simple definition of done in my inbox:
A good working definition of “Done”: Someone’s need was met.
– Mike Burrows (@asplake) , January 29, 2016
Someone in this context should be taken as everyone that has a stake on the feature/user story:
- The Product Owner’s Acceptance criteria are met.
- The Business need will be fulfilled by the developed feature.
- The Quality Champion’s criteria for well tested feature are met.
- The (future) Maintenance team would be able to handle any required fixes or maintenance on this code without any difficulties.
- The Build Integrator will not find any issues with the generated package.
- (insert your other stakeholder group here together with their concern)
The definition of done (DoD) need not be a list. What is needed is for the team members to understand that Done means the feature is useful for everyone who is interested in it, may it be directly or indirectly. If that is not possible then the team needs to make sure they arrive to that point as part of the Inspect & Adapt mandate of agile methodologies.