Recently I had the opportunity to meet a group of requirements specialists.
They were interested in
learning about Agility from the point of view of requirements gathering.
They were keen on getting all the right requirements documented so the developers
can have all they
need to get their work done.
Unfortunately, the more time and effort we spend up-front trying to get the requirement
fully documented,
the more we will find ourselves failing at it. A better approach is to get the requirements
documented at a
fairly high level, highlighting what you may thing as major and/or important features.
Then you can delve into
details right before the implementation.
A great book to read in this area is Mike Cohn?s ?User Stories Applied.?
So, what do I expect from a requirements document. Rather than providing answer to
all my questions, I
would like for it to help me ask the right questions when I am ready to delve into
the implementation.
A great requirements document helps me not with right answers, but with right questions.
