Definition of DONE in Software Developent

Let’s imagine, that at the end of every iteration in SCRUM or any other Agile Software Development method, the developer is coming to you and saying: “I’m done with this functionality!” But you of course ask: “What do you mean done? Are you done or done done?”

What do I want to say here: Software developers think that software development begins and ends with them. It’s actually not really false, but…
The software development is much bigger than only writing the code. Code by itself isn’t that useful. When developing team is stating define Definition of Done (DoD), it will be much more than “just coding”.

Example Definition of Done

Development / Coding

  • Code is written with unit tests
  • Code has been merged to Main
  • Code reviewed by someone other than the author

Testing / Deployment

  • Written QA tests
  • Tested by QC
  • Tested by QA
  • Written UI tests
  • Accepted by Product Owner
  • Load tested Deployed to Production

As you can see, the real Done functionality contains much more steps, as just only code. And how to determine this Definition of Done (DoD)?

 Defining Definition of Done (DoD)

  • Get the team together before or just at the project beginning
  • Start to discus in which phase your functionality can be named as DONE
  • Try to avoid ambiguity and differences in definition
  • Write it down!
  • All team members should follow the DoD

So in next, when developer will come and say:”I’m done!”, all will know exactly what does it mean.

Related Post

3 Levels of requirements in Agile development In Software Development Requirements have 3 levels: - expanded description of customers business - business point of view requirements - functionalities which should be made in our application Example: “We need a tool for selecting big data...
9 main Agile software development Methodologies Agile Modeling Set of concepts, principles and techniques (practices) that enables you to quickly and easily perform design and documentation for software development projects. Does not include detailed instructions on designing, contains descript...
What characteristic should requirement possess? All significant requirements included. No items have been left for future definition. Incompete if: - Non functional requirements missing; - Hidden assumptions; - Too general statements Conflicting terminology, contradictory required ac...
Understanding Product Owner Role Responsibility Must have a Shared Vision Developing Winning product Product Owner controls the development effort in order to create a product Other Features A) Create Product Vision B) Maintaining the product backlog C) Release pla...