Business Requirements

• Identify sprint sized 'user stories' using Use case outline sentence 'As a xxx I wish to do yyyy so that'

• Use cases diagrams - use <<includes>> for all but the primary user story -

• Primary user stories written by customers

• All user stories written in business terms

• Programmer estimates size

• Product Owner assigns priority

• Schedule user stories in each sprint

• after implementation, these <<included>> use cases can just be assumed to be part of the parent.

 

Agile Analysis

• Use case details - pre-conditions, triggers, and outcomes not necessarily defined

• Business Rules - are defined in code by the programmer without any formal input

• For moderate sized programs it is recommended that one of these strategies is adopted:

  • All the 'necessary' use cases be outlined and agreed at the begginning.

  • All business Objects be formally identified and at least named at the begginning.

 

Agile Implementation

• Implementation - programmer driven

• Acceptance  - users testing the system report changes, which get added to the list of packs for selection at the next suitable sprint.