Definition of Ready (DoR) for a Data Warehouse Team
The definition of ready (DoR) for a team typically calls out the analysis work to be done before a work item is brought into the team. A team’s DoR protects them from poor-quality requests, typically poorly described requirements. The DoR is an agile quality gate that work requests must pass through to reach the team, as shown in Figure 1. There is a corresponding definition of done (DoD) that the team must meet for their work to continue downstream in the overall process.
Figure 1. A team’s DoR and DoD.
Figure 2 provides an example of a DoR for an agile data warehouse team. Notice how this DoR includes criteria for both a question story and for a defect report, the two types of work items on their backlog. This team operates in a regulated environment and, as a result, works with an independent testing team that produces defect reports describing potential issues found.
Figure 2. Example definition of ready (DoR) for an agile data warehouse team.
A question story must meet the following criteria:
A defect report must meet the following criteria:
|
Figure 3 depicts an example of a DoR for a data warehousing team following a continuous delivery WoW rather than an agile one. One of the benefits of working this way is that the look-ahead data analysis effort required to support short sprints simply becomes something that the team performs once they bring the work item into the team. As a result, the criteria for a question story are much simpler. The criteria for a defect report remain the same because removing sprints doesn’t change the timing or the way a potential defect is reported to the team.
Figure 3. Example definition of ready (DoR) for a continuous data warehouse team.
A question story must meet the following criteria:
A defect report must meet the following criteria:
|
Source
Material for this article was adapted from Not Just Data: How To Deliver Continuous Enterprise Data.