"break them into atomic tasks": I didn't think this sort of hyper-specialization would work in a fast-paced environment. It seems to treat developers as just English-to-C++ translators.
My experience has been that specifying in great detail HOW to do things (as SCRUM does for s/w development) doesn't work as well as specifying WHAT to do and letting people figure out how to do it, but holding them accountable for results. The latter style will naturally result in the evolution of automated systems such as regressions, quantitative user feedback, beta progam etc to ensure that the work got done and quality is maintained.
One should have some structure and avoid reinventing the wheel, but I'm skeptical of detailed recipes like this.