| But there is no one single such triangle. Many people have in mind this version of the "quality triangle" which we were discussing (not a Project Management triangle which I agree is more on point). You get that a lot if search for "quality triangle": https://www.google.fr/search?tbm=isch&q=quality+triangle Why is it commonly assumed that quality and cost and time are opposed to each other? The Capers Jones books have one idea throughout, that is backed by data: for Software, quality is positively correlated with reduced time-to-market, low defects, and reduced costs. > The practices that help to ensure quality that are outside the triangle’s intent as a guideline There is a chapter about that in EoSQ, where each and every practice are measured and classified by efficiency, like TDD and code reviews. It's very interesting. > The result is that he tends towards promoting older practices that help quality but don’t have much impact on whether you’re building the right thing in the first place. Yes. I find he puts way too much faith in "off the shelf" software as the last bullet we may have. tl;dr Capers Jones disprove the "quality triangle" big time, which is a product of intuitive reasoning without any basis, which doesn't apply to software. Just look at Intel at this very moment. |