QASymphony / Blog / Acceptance Test Driven Development (ATDD) in Agile Environments
Acceptance Test Driven Development (ATDD) in Agile Environments
Acceptance Test Driven Development (ATDD) is an increasingly popular development method for agile teams. ATDD is closely related to Test Driven Development (TDD), but stands out because of its highly collaborative approach. Acceptance Test Driven Development requires participation from customer-facing team members to help provide end user stories to the development/testing team. These stories are distilled into Acceptance Tests that guide the development process.
Let’s take a look at three reasons that Acceptance Test Driven Development is ideal in an agile environment:
ATDD closes the loop between product and dev teams. By nature, this method involves bringing in multiple teams to help make the project a success The beauty of this type of collaboration up front is that the development team can go into the project with a clear picture of the end user’s needs in mind.
ATDD increases efficiency in the development process. Starting with a clear understanding of a specific requirement can speed up the development process significantly.
ATDD promotes a shared understanding of “complete.” When the whole team is involved in creating the requirements for the end goal, there is a lot more clarity on what the finished project should look like. No time is wasted on miscommunication, unmet expectations, or last minutes changes due to lack of understanding about the end user.
Interested in implementing Acceptance Test Driven Development with your team?
Join our Senior Product Manager Kevin Dunne next week for our webinar – “Tips, Truths, and Misconceptions of Acceptance Test Driven Development.” Kevin will be joined by Adam Satterfield, VP of QA at BetterCloud and outspoken practitioner of ATDD. Adam will draw on his experience managing quality at organizations using ATDD. Kevin and Adam will be giving practical advice on how to implement Acceptance Test Driven Development, as well as clarifying what ATDD will and won’t do for your team.