4 Who does what and when
This chapter covers
- The activities that make up the BDD approach
- Using BDD with Scrum and other methods
- Using BDD with distributed teams
- Using BDD for fixed-scope and regulated projects
In the previous chapters, we discussed the importance of collaboration for a BDD approach to be successful. In this chapter, we will show how BDD can be integrated into the development process and answer some common questions, like “Who should write the scenarios?”, “Who do we need to participate in the requirement workshops?”, and “Should the testers or the developers automate the scenarios?”.
In this chapter we’re going to describe the BDD approach in more detail. We’ll also provide some examples of how BDD has been successfully adopted by various organizations using different development processes. Don’t treat these as best practice checklists, but rather as starting points that allow you to develop a process that fits your project.
Remember that every project is different. They follow different development processes (such as Scrum or Kanban). They are integrated into a company culture that has its own definition of what each role is responsible for. For example, how much development skill should a tester have? Individual team members will have different backgrounds and personalities.
The most successful projects consider all these factors when defining their development process (and understand that this process has to be reviewed and adapted as necessary).