All About Agile | Agile Development Made Easy

Atomic Requirements

by Scott Sehlhorst, 14 September 2010 | The Agile Blogosphere

This post is from Tyner Blain by Scott Sehlhorst. Click here to see the original post in full.

Each requirement you write represents a single market need, that you either satisfy or fail to satisfy.  A well written requirement is independently deliverable and represents an incremental increase in the value of your software.  That is the definition of an atomic requirement.  Read on to see why atomic requirements are important.

Atomic Requirements – Revisiting

As part of the ongoing series, Writing Good Requirements – The Big Ten Rules, I wrote about the importance of atomic requirements first in 2006.  That article touched on only one aspect of atomic requirements – being able to ask “is it done?”

Writing atomic requirements is important from two perspectives – delivering value to your customers, and operating efficiently.  You get benefits both operationally,...

read more


Leave a Reply

What is 10 + 3 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)