QuestionQ7

Agile software development and Test Techniques

You are working on a project to develop an application that lets users collaborate through bespoke online whiteboards. The first release, which delivered core functionality, revealed misunderstandings of the user stories among testers, developers, and the product owner during sprint development. Since that release, the developers have agreed to use a TDD approach for future software development.

Creation of the product backlog for the second release is underway, and you have recommended that the project stakeholders adopt an ATDD approach for the backlog’s user stories. What would be a GOOD REASON for this recommendation?

Explanation

ATDD defines acceptance-test examples collaboratively among the product owner, developers, and testers. These examples make the intended behavior and acceptance criteria of each user story explicit, creating a shared understanding and helping prevent the misunderstandings experienced in the first release.

Community Discussion

No comments yet. Be the first to start the discussion!