Please enable JavaScript.
Coggle requires JavaScript to display documents.
Agile Requirements Definition - Coggle Diagram
Agile Requirements Definition
Descvribing the need for the product
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
each user strory will be fully explored
as development progresses
listing the required product features
high level document
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
ordering the 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
crucial for the release
Should-Have features
important but can be replaced
by some workarounds
Could-Have features
can be left out from release if
team runs out development time
Would-Have features
could be moved to future release
desidered features
refining the requirements
changes to requirements
activitiy made with the customer
at the end of iteration complete