Definition of Done when working in DEV and PRO environments
Hello there
I have a doubt when establishing a DoD for a team who works in
Sometimes the scope you work in is only the DEV environment, until a project is completed.
In that sense, we won't be able to publish to PRO until other product backlog items are completed, or the client gives the ok to do so.
How do we handle this duality in the Definition of Done?
Example: We are working on a web redesign, and until the client gives the go-ahead to the entire site, there is no publication in production, and therefore, the full value has not been delivered.
Should we consider only the point when a product backlog item has been developed, tested and approved in the DEV environment, and therefore it is potentially releasable?
or should we include in our DoD the point when a product backlog item has been also released into the production environment?
Thanks!
These lines are from the Scrum Guide's section that explains the Definition of Done.
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.
The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment.
No where does it say that anything has to be released to a specific environment. Nor does it even say that it has to be released at all. It is all about making clear what work has been done to produce a usable increment of quality and value. Some organizations will include the releasing of the increment to specific environments but that is not something I advocate. I advocate that the Definition of Done include statements that show the work and effort that has gone into the increment. For example,
- All code has been reviewed and approved by 2 or more developers
- All automated tests have been executed against the code and any issues have been addressed
- All code is submitted to the code repository
Those are the type of descriptions that illustrate the work done to ensure that quality was delivered. The main goal of a Definition of Done is so that anyone can read it and understand what work has been accomplished in the creation of the increment, the quality measures used, the conditions that must be met in order for the the Developers to say "we have completed our work and this increment is done".
How do we handle this duality in the Definition of Done?
You don't. It's exposed a real-world issue, and that issue ought to be resolved. The issue appears to be that either the Developers are not good enough to assure work is Done and/or the PO cannot be trusted. That is evidently the perception. A client must give the team's work some sort of benediction and blessing. The "project" model is used as a crutch for all of this and the Sprint has evaporated. Find out why.