Agile Requirements Definition

  1. Descvribing the need for the product
  1. listing the required product features
  1. ordering the requirements
  1. refining the requirements

customer describe business need
for the product

generation of use stories

prospective of customer

prospective of end user

just enough information
for a project team to determine the
amount of work

high level document

each user strory will be fully explored
as development progresses

road-map for the project

scrum

product backlog

owned by the product owner

mantaining any changes
customer needs

mantain any changes due to
technical requirements

based on importance for the customer

customer could tag each requirement

with a priority flag as low, medium, high

using MoSCoW technique

Must-Have features

Should-Have features

Could-Have features

important but can be replaced
by some workarounds

Would-Have features

could be moved to future release

can be left out from release if
team runs out development time

crucial for the release

desidered features

changes to requirements

activitiy made with the customer
at the end of iteration complete