Member-only story
ETL : Definition-of-Done (DoD) vs Definition-of-Ready (DoR)
As an ETL developer, I believe that planning for the Definition of Done (DoD) and the Definition of Ready (DoR) is crucial for ensuring the success of an ETL pipeline project. Here are some steps that I would follow to plan for DoD and DoR for an ETL pipeline project:
Understand the requirements
The first step is to understand the requirements of the ETL pipeline project. This includes understanding the data sources, the target system, the transformation rules, and the expected output.
Define the DoD
Based on the requirements, I would work with the project team to define the DoD for the ETL pipeline project. The DoD should be a shared understanding among the team members of when a product increment is ready for release. It should define the criteria that a product increment must meet for the team to consider it complete and ready for customers. Some examples of what could be included in a DoD are:
- All code has been thoroughly tested via unit, integration, and end-to-end tests.
- Product increment has been deployed to a staging environment and tested by the team.
- All errors have been resolved.
- All release documentation has been written and edited ¹.
Define the DoR
Once the DoD is defined, I would work with the project team to define the DoR for the ETL pipeline project. The DoR should outline the criteria for a product backlog item to even be considered by the team for bringing into their sprint. It should help the team identify when a product backlog item is ready to work on. Although the Scrum Guide does not mention a definition of ready, some teams find it to be a valuable tool for managing their work. Some examples of what might be included in a DoR are:
- The PBI is written in a clear, concise way.
- Related acceptance criteria have been defined and are testable.
- Any dependencies have been identified and addressed.
- All necessary stakeholders have approved the PBI ¹².
