DA 202 – Writing Acceptance Criteria: A Disciplined Approach
Disciplined agile project teams capture detailed requirements in the form of acceptance criteria, or so the rhetoric goes. But how do they do this? Most solutions have a wide range of stakeholders who have an even wider range of concerns. This implies that the requirements for a given solution will potentially be very robust and therefore require both skill and discipline to define. This workshop overviews the fundamental skills required to elicit and capture stakeholder requirements in the form of acceptance criteria.
- Agile practitioners who want to learn how to effectively capture and implement acceptance criteria
- Introduction to acceptance tests
- Acceptance test driven development (ATDD)/Behavior Driven Development (BDD)
- ATTD throughout the lifecycle
- End-user acceptance criteria for business logic, the user interface, and for data
- Technical acceptance criteria
- Capturing acceptance criteria
- Level: Introductory
- Length: One day – 7 hours of classroom time plus breaks.
- Approach: For each major topic in the agenda there will be instruction followed by group work.
- Prerequisites: Basic understanding of Disciplined Agile Delivery (DAD) useful but not required.
- Class size: Ideally 10 to 15, although up to 20 if the room allows.
- Classroom requirements: For the students a table layout is preferred. Ideally there should be tables of 4-6 people with sufficient space between them so that students can easily move about the room. For the instructor a screen, projector, and writing space (whiteboards or flipcharts).
Most people will first take DA 201 – User Stories: A Disciplined Approach and then follow it with this one. These two workshops are typically taught back-to-back in customer organizations.