Most of you should be familiar with Test-Driven Development (TDD), an Agile approach where you write a unit test before actually writing the code that should be verified. In this blog post, Jeffrey Davidson use the same concept and proposes a Test-Driven Retrospectives approach to ensure that this Scrum activity provides real improvements.
Jeffrey Davidson thinks that “retrospectives are the single best thing about Agile and Scrum”. In a Test-Driven Retrospective, the team starts the retrospective by choosing a key item to work on. Then the following question is asked: “How could you prove that the objective has been achieved?” You can use around 20 minutes to clarify the goal. Then the team will individually write acceptance tests before sharing and discussing them. Responsibilities for completing the goal are assigned.