Agile2014 has ended
Back To Schedule
Monday, July 28 • 10:45 - 12:00
How to use ATDD to help deliver quality software in Kanban or Scrum process. (Adam Yuret) LIMITED

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

Limited Capacity seats available

How much time and effort in even agile software development organizations is lost to rework, defects, technical debt and building the wrong things?

How much of this failure demand is caused by not talking to each other?

Acceptance Test Driven Development is one way of talking to each other that can help us mitigate some of those risks in our development process.

ATDD is an collaborative approach to achieving shared-understanding using concrete examples discovered collaboratively.

During this session we'll cover:

What is a user story? (You think you know but you might be surprised)

The process consists of the following steps:

- Story Workshops for every story in the prioritized backlog are conducted wherein a tester, a programmer and a customer (or proxy if that's all that is available) have an informal conversation about what the meaning and intent of the story are.

Asking "What does x mean?" types of questions and capturing user/business centered acceptance criteria. Using those criteria as a splitting heuristic and other approaches to split stories into small vertical slices of value using a slightly modified INVST model for user stories. Further distilling those acceptance criteria into concrete examples (tests) to help guide development

- Taking the byproducts of the ATDD story workshop and turning them into the following useful tools for informing development:

- Acceptance level test automation using unit tests or domain specific language tool (e.g. Cucumber, FitNesse etc.)

- Concrete examples to help guide paired dev/test development of production code.

- A guide for helping create a zero-tolerance policy for acceptance level defects.

This workshop will start with a discussion of ATDD basics followed by a mock user story workshop. We'll deconstruct a user story, collaboratively identify acceptance criteria and concrete examples. Wrapping up with a brief discussion of ATDD-friendly tools.

We'll go beyond these concepts and workshop to answer the often unanswered questions:

"Sure but who has time for all this?"

"We're sprinting so we have to develop as fast as possible, we don't have time to talk to each other?"

"We're doing Kanban, when do we have workshops if we have no structured planning meeting ritual?

"Isn't this big design up front?"

We'll also touch upon what a user story workshop isn't and ATDD anti-patterns to be avoided.

avatar for Adam Yuret

Adam Yuret

Founder/Consultant, Context Driven Agility
Adam Yuret is an experienced systems thinker who has consulted small non-profits and fortune 100 clients on adopting context-driven systems to solving difficult problems. Adam started Context Driven Agility in 2010 to share his passion for humanistic flow-based systems full time... Read More →

Monday July 28, 2014 10:45 - 12:00 EDT
Osceola B