User Story Life Cycle is Not Enough

By | 2012-02-20T21:57:41+00:00

The usual agile requirements life cycle consists of three simple states: “not started”, “in progress” and “done”. This is not enough! These steps only cover the software development part of the requirements life cycle. Do not forget about the stages before and after. First requirements are new, then they are analyzed and estimated, then they are commited for delivery in a sprint. After that comes the states mentioned above. After that comes release, deployment, maintenance and eventually retirement. Have a look at the Requirements Abstraction Model.

Category: Requirements Engineering

About Greger Wikstrand

Greger Wikstrand, Ph.D. M.Sc. is a TOGAF 9 certified enterprise architect with an interest in e-heatlh, m-health and all things agile as well as processes, methods and tools. Greger Wikstrand works as a consultant at Capgemini where he alternates between enterprise agile coaching, problem solving and designing large scale e-health services ...

Leave a Reply

Your email address will not be published. Required fields are marked *