For DoD, it is worth having a discussion at start of project, what it is, why its that and what value it can bring. Here’s a few variations I’ve seen, its okay to use different one’s on different projects but essential to have the discussion and align.
- Developer has finished coding - not even in dev yet. This one is not great.
- Developer coded and feature in build ready for testing. Has its use.
- Developer coded and dev automated tests run succesfully. Higher value.
- Developed, automated test in place and verified by tester.
- Developed, automated test, verified and testing explored. i.e Done means its fairly safe to go to production - often common understanding of done. Advanced usage but makes a lot of sense.
On the other element, I do tend to find the concepts of SDLC and the idea of a testing phase more associated with waterfall models and not so much used in Agile type models.
There is quite a bit of discussion on holistic testing out there that I have found useful, they vary significantly though and the term far from means the same thing for every but there can be value in applying some elements from those discussions. Here is a visual I have used, it is cyclic even though it looks more sdlc style and rare all of those would apply to a single project but it may have a few ideas of use to others.
