In this episode, we move on from the development side of Acceptance Test-Driven Development and turn to the fundamentals of how these 'requirements' actually get written in the first place.

We look at the tricky question of when exactly these 'detailed' requirements should get written on a project, how detailed they should be and where they belong in the process and WHO exactly should be writing them.

We'll consider the impact this 'additional' work might have on our team's velocity and how it actually helps planning and the accuracy of our estimates bringing greater predictability through the 'shifting left' of the QA process.

Enjoy the chance to be a fly-on-the-wall, watching along as our intrepid team wrestle with the process of writing up-front new requirements specific enough and through example, for the development team to carry on the work of developing their HP-35 calculator.