Planning Game – User StoriesStory Capture• Requirements are broken down into chunks that can be delivered in subsequent iterations• Stories are captured on index cards or in a Story Studio repository• Stories have both a narrative part and matching acceptance tests• Stories are not traditional documents, they represent conversationsStory FormatThe story needs: • Title• Concise problem statement“As <role> I want <function> so that <business value>”• You may find it useful to record other notes, screen layout, truth name, date, ref number, etc.Acceptance Criteria• To prevent developers expanding scope the acceptance tests need to be clearly stated• Simple format is:When I do this action, I expect this result• The project should aim to build acceptance tests into a suite that can be automated• More detailed tests may need to be defined during iteration
< Page 7 | Page 9 >