People of the Team, Unite! Apply ATDD!
Within agile teams we see that the team members must understand all roles in the team. From business analyst to acceptance tester and from architect to developer, a team member must play a diversity of roles. However, at the same time, each team member will have his or her own “default” or favorite activity. To a tester this will obviously be testing.
When we apply Acceptance Test Driven Development or Specification by Example, the tester will play an important role at the beginning of the sprint. Especially during this phase, the refinement, the tester will need to be aware of all team roles.
What is the case when we apply ATDD? One of the main principles is that the elaboration of user stories is done into test cases instead of design specs. This leads to two initial advantages: 1- The elaboration is implicitly “reviewed” and 2- The design phase is skipped so savings on effort. But there are more advantages: ATDD and SBE lead to common understanding (the whole team understands what should be done), Acceptance Test Cases (the specs) and living documentation (each new change must be made to the test cases first).
But this phenomenon not only occurs in agile development; in linear development too we can apply this techniques.
In this presentation I will elaborate on the advantages of ATDD
In the workshop, I will divide the audience into two groups. Each of these groups will get the same assignments, however, the approach will differ.
The aim is to design acceptance test cases to test a web site. One group gets the assignment to work according to the V-model and will therefore receive a functional design as input. The second group will be given the task to work according the agile approach and will get user stories that describe the same functionality. For both groups I will be the SME or Product owner, so I will supply additional information if needed.
The two groups may not communicate with each other. Each group is asked to create acceptance test cases according to the principles of ATDD. The groups are asked to record their experiences regarding process, time and quality.
At the end of the workshop, both groups will share experiences and will determine whether the assumption that ATDD is applicable in both agile and linear devlopment is correct.People-of-the-Team-Unite-V0.8