Defining the DONE
Avinash Bais
Service Management & Project Delivery | Program & Project Execution | Enhancing Operational Success
Defining the DONE Criteria
I think this is the first and foremost process to be in place from Day-1.
What is DONE Criteria ?
DONE criteria are high level check list items which needs to be satisfied in order to claim a story is DONE. DONE Criteria should have technical, process, functional, non-functional, configuration aspects of the software. DONE criteria forces teams to take holistic view on the stories rather then code completing the feature.
Some of the common aspects of done criteria
- All acceptance criteria met. (Functional)
- Performance not degraded. (Non Functional)
- Code coverage achieved and all acceptance tests automation. (Technical )
- All build passed and application deployed on UAT/Staging environment. (Environment/Configuration)
- Exploratory testing performed and QA signed off.
- Demoed to stake holders on proper environment. (Process)
- All known bugs closed and tested (Process)
By doing this teams will make sure that software produced is of great quality and all aspects of the applications are taken care. Doing this repeatedly will make sure testers are not doing catchup but they are part of the story and sign off process. Software produced in the end can be released and should be production ready.
Its termed as "Definition of done"; apart its not always necessary that all bugs status should be 'closed', however the product with prio 1 / 2 bugs are not potential shippable product.The product either with very low severity and priority else of postponed due acceptable reasons could be a potential shippable product. ~ All the bugs should be tested and closed.