By Elisabeth Hendrickson
Just ten years ago, agile was still considered radical. Fringe. Weird. The standard approach to delivering software involved phases: analyze, then design, then code, then test. Integration and testing happened only at the end of the cycle. The full development cycle took months or years.
If you have never worked in an organization with long cycles and discrete phases, the idea may seem a little weird now, but it was the standard a decade ago.
Back when phases were the norm and agile was still new, the agile community was mostly programmer-centric. Janet and Lisa and a few others from quality and testing were there. However, many in the agile community felt that QA had become irrelevant. They were wrong, of course. ...