ATDD is a Whole Team Approach – A Real Case Study
Collaboration is one of the core values of agile, but what do you do if it’s not happening? During his career, Raj Subramanian has experienced lack of collaboration between developers, QA, and business folks; little clarity in requirements; frequent scope creep; no visibility on testing; and defects found late in the project lifecycle. To tackle these problems, Raj adopted Acceptance Test-Driven Development (ATDD) as a way to mitigate some of these issues. Often seen as synonymous with Behavior-Driven Development (BDD) and Test-Driven Development (TDD), the main distinction of ATDD is its focus on making developers, testers, business, product owners, and other stakeholders collaborate and agree on a clear understanding of what is needed. Join Raj as he shares the problems his team had and how he trained the team on different practices thus re-establishing the mindset of One Team, One Goal. He shares the process changes that happened due to ATDD, how his team leveraged test automation, and the lessons they learned from the implementation. This session is based on his real-life experiences of how a single tester can make a huge impact in a team if they recognize collaboration is the key to success.