For example, ETL jobs went from 2.3 jobs to 3.8 over from sprint two which is a six weeks cycle. So almost immediate we had efficiency gains while we follow the process. We follow the process of getting the validation through the prototyping and the business modeling and the data profiling in the Sprint 0 work and using up the consensus tool. We can see that change request in this case fall, and so what we see is that the defect rate is zero within a release.
Certainly across releases we have seen a couple of cases where we were able to achieve zero defects, right out of the gate. So as the teams get more familiar with and more comfortable with the methodology and the processes and embedding, coupling well with the consensus tool, we end up with high value, lower cost and a much higher quality product.
So the tools can really help because we get a common definition used across the different component tree and the idea is that every project I would encourage you to bring in Sprint 0 into every project you do for six weeks. Use the prototyping techniques. Use the profiling to find your skeletons. This is going to allow you to hit that home run every time.
Every time we do this the business says that’s exactly what I want. The user acceptance step is almost rubber stamping because they have seen the solution two, three, four times before it actually goes live, and in terms of walking the walk, because of we’re so confident in how we estimate and gather requirements and in our methodology, we’re always willing to fix our price for the work.