October 2012
Intermediate to advanced
384 pages
12h 3m
English
Traditional software development directed us to hand off a code-complete application to testers at the end of a lengthy development cycle. As our craft improved, we sought shorter development cycles, but we still handed off to testers. As we embraced Scrum, we removed the handoff by building a cross-functional Development Team able to perform all of the required activities. We’re getting better, but I contend that there is still room for improvement.
The physics of software development tells us that testers must have a stable, finished piece of software to click and poke. On the surface, this sounds like an honest appraisal. I mean, why bother wasting time testing software that isn’t code complete, ...
Read now
Unlock full access