by Ryan Walker •

Acceptance Test Driven Planning

  1. BRAIN DUMP High level brain dump of stories (role & action)

  2. STORY DEFINITION After the story dump list is complete, add a few sentences to describe each story (the idea is that there should be just enough information to serve as a token for a conversation that should take place as we get closer to implementation)

  3. RELEASE STORIES SELECTION Select some stories for the initial release, err on the side of fewer stories.

  4. ITERATION STORIES SELECTION Select just enough stories to result in working software that we can interact with in a meaningful way (maybe 2-3).

  5. ITERATION PLANNING MEETING Convert the stories in the iteration into cucumber features that consisting of:

    • FEATURE TITLE
    • FEATURE NARRATIVE (using Connextra format: as a … i want to … so that I…)
    • ACCEPTANCE CRITERIA (write cucumber scenarios + scenario outlines).
Filed under Agile Product Development Software Development