2001 Continuous Integration Systems Review Test-Driven Development 
Coveros
FEBRUARY 16, 2021
Take a moment to think about where you were in February of 2001—at the inception of the Agile Manifesto. I was with a privately held software engineering firm focused on helping organizations transform their software testing capabilities. Have we, as software testing professionals, advanced our craft? 2011–2020 and Beyond.
Coveros
FEBRUARY 26, 2021
While there were definitely some new concepts introduced in the article—like pair programming and test-driven development—the overall philosophy hit home in a big way. However, getting developers to test their own code was always a struggle. When the Agile Manifesto was first published in 2001, I smiled.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
James Shore
APRIL 26, 2021
Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. Continuous Integration. Next, review the design and make improvements. Mob Programming.
James Shore
JUNE 7, 2021
Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. For an excellent and practical guide to incident response, see Site Reliability Engineering: How Google Runs Production Systems [Beyer et al.
LeanEssays
JUNE 5, 2015
Instead, Modig and Ahlström demonstrate that lean is about flow efficiency – that is, the efficiency with which a unit of work (a flow unit) moves through the system. In my case, the dental system was focused on the efficiency of the lab’s milling machine – no doubt an expensive piece of equipment. Consider our dental experience.
Expert insights. Personalized for you.
52 
Let's personalize your content