I am currently working on a project in which a so-called Waterfall-Scrum process is completed. This includes one week of development and one week of testing.
Each team (currently 7 teams building on each other!) currently has its own Definition of Ready and Definition of Done. This means that there are often strong problems in the process of testing and delivery to the next stage.
Problems that arise:
- Partly late deliveries, from development to the next development stage
- Unclear definition of when, what, where to ship (even with different build times)
- Unclear circumstances which team tests when, where, what. It starts with the team that should use the Unit Test, only doing Functional Tests.
- However, other teams build on the only partially tested products. This results in a spiral of mistakes.
- Some teams have a staging process, others only partially. Pre-production is missing.
Approach (My suggestion)
- Analysis of the process with all participants
- Use a new global definition of Ready and Done that clearly defines all teams when something needs to be done.
- Standardize the staging problem by introducing clear structures and unit testing. This allows you to intervene at an early stage in case of misconduct.
I've thought about some points, but I need your advice here:
The team's own definition of Ready and Done should remain in place. The global definition of Ready and Done should only describe the individual stages (delivery to the next test days).
- Am I right with my approach?
- Should a Global Definition of Ready and Done be able to solve problems within delivery and testing?
- Do you have other approaches?
- Should you only adapt the cross-team definition of Ready and Done?
Perhaps one or the other has already experienced something similar in another project?