article thumbnail

Software Testing and Agile

Coveros

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.

article thumbnail

Taking an Extreme Approach to Software

Coveros

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

AoAD2 Practice: Pair Programming

James Shore

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. Cockburn and Williams 2001] Every team is different, so take these results with a grain of salt. Test-Driven Development.

article thumbnail

AoAD2 Practice: Incremental Design

James Shore

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. Test-driven development encourages you to think about and improve your design at nearly every step.

article thumbnail

AoAD2 Practice: Incident Analysis

James Shore

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.

article thumbnail

Agile vs Waterfall: Key Differences And Definition?—?Which Model Is Better?

Codegiant

The Agile methodology definition was introduced by 17 software developers gathered in Utah back in 2001. Due to Agile’s highly encouraging face-to-face interaction , you can bring everybody on the same page. Dynamic Systems Development Method ?—?Since Adaptive System Development ?—?as

Agile 52
article thumbnail

The Art of Agile Development, Second Edition

James Shore

So, what allows me to do this—what allows me to do this show, this software development show every week, and what allows me to write this book—is the people who hire me for training and consulting. First, business analysts would interview stakeholders and document the system requirements. The project launched in June 2001.

Agile 99