article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

Test-Driven Development. It’s test-driven development, and it actually delivers these results. Test-driven development, , or TDD, is a rapid cycle of testing, coding, and refactoring. Test-driven development applies the same principle to programmers’ intention.

article thumbnail

AoAD2 Practice: Slack

James Shore

If our commitment is at risk, shouldn’t we temporarily stop pair programming, refactoring, test-driven development, etc.? Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency [DeMarco 2002] provides a compelling case for providing slack throughout the organization. Further Reading.

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: Whole Team

James Shore

Until then, development on an Agile team looks similar to development on any other team. Test Driven Development. They use test-driven development to write tests, implement code, refactor, and incrementally design and architect the software. Test Driven Development.

article thumbnail

AoAD2 Practice: Pair Programming

James Shore

Test-Driven Development. Take small steps—test-driven development works well—and talk about your assumptions, short-term goals, general direction, and any relevant history of the feature or project. Test-Driven Development. Use test-driven development and take very small steps.

article thumbnail

AoAD2 Practice: Incremental Design

James Shore

Test-Driven Development. Test-driven development encourages you to think about and improve your design at nearly every step. Test-Driven Development. If you’ve practiced test-driven development, you’ve practiced incremental design, at least at the level of a single module or class.

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. Seventeen months later, in November 2002, “solid requirements” had been established. million of which were completely unrecoverable.

Agile 99