Definition of Done
The Definition of Done is our shared checklist for what 'finished' really means. A feature is not done when the code is written -- it is done when it is tested, reviewed, documented and genuinely ready for your users.
Agreeing this up front prevents the awkward gap between 'developed' and 'usable', and means that when we say something is complete, you can trust exactly what that includes.
What 'Done' Typically Includes
Our standard checklist applies to every piece of work so quality stays consistent across the whole project.
- The code is written and meets the acceptance criteria.
- It has been reviewed by another developer.
- Automated and manual tests pass.
- Any necessary documentation is updated.
Why It Protects You
A clear, shared definition removes ambiguity and keeps quality from being quietly traded away under pressure.
- You know precisely what each completed item includes.
- Quality stays consistent even when deadlines loom.
- There are fewer surprises and less rework after launch.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.