Remove 2001 Remove Microservices Remove SCRUM Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Incident Analysis

James Shore

Kerth 2001] (ch. In this case, a closer look at the event reveals that, although the team used test-driven development and pairing for production code, they didn’t apply that standard to their scripts. Or, “we have microservices, not a monolith.” Incident analysis always looks at the system, not individuals.

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. In 2001, 17 of the lightweight methodology proponents met at a ski resort in Utah to discuss unifying their efforts. Get me some Agile.”.

Agile 99
article thumbnail

Lean Software Development: The Backstory

LeanEssays

In 1999, Kent Beck proposed a radically new approach to software development in the book “Extreme Programming Explained” (Beck, 1999). In 2001 the Agile Manifesto (Beck et al., 2001) gave this new approach a name – “Agile.” Put the tests into a test harness for ongoing code verification.