phyfe
07-11-2006, 02:32 PM
Just Enough Requirement Management by Alan M. Davis (http://www.amazon.com/gp/product/0932633641/sr=8-1/qid=1152646606/ref=pd_bbs_1/102-6098209-0757707?ie=UTF8)
I'll start by saying that I'm primarily a developer, however I have worked on several projects as a team lead, so I have worked closely with Project Managers and Business Analysts. The whole Requirements process, in my experience, has always been somewhat frustrating but that is a whole other topic.
Premise of the book.
Alan defines the requirements process in four stages; Elicitation, Triage, Specification and Change. Within this process he discusses the importance of being able to quickly view a list of requirements whether they be contenders during elicitation or part of a particular release after specification. All the while he stresses the importance of only doing just enough.
There is a great section that defines different types of requirement to requirement dependencies. As well there is a whole section on how to determine if the selection of candidate requirements for a release can be done within the schedule and the budget.
My opinion
I feel that Alan is spot on with his "Just Enough" concept of not only gathering requirements but of also maintaining and utilizing them throughout a project life-cycle. I've been in too many situations where there was not enough focus on requirements and they became lost and forgotten. Other times it was too much, with pages and pages of junk.
I highly recommend this book it's short, concise and to the point. It's...well...Just enough. :)
I'll start by saying that I'm primarily a developer, however I have worked on several projects as a team lead, so I have worked closely with Project Managers and Business Analysts. The whole Requirements process, in my experience, has always been somewhat frustrating but that is a whole other topic.
Premise of the book.
Alan defines the requirements process in four stages; Elicitation, Triage, Specification and Change. Within this process he discusses the importance of being able to quickly view a list of requirements whether they be contenders during elicitation or part of a particular release after specification. All the while he stresses the importance of only doing just enough.
There is a great section that defines different types of requirement to requirement dependencies. As well there is a whole section on how to determine if the selection of candidate requirements for a release can be done within the schedule and the budget.
My opinion
I feel that Alan is spot on with his "Just Enough" concept of not only gathering requirements but of also maintaining and utilizing them throughout a project life-cycle. I've been in too many situations where there was not enough focus on requirements and they became lost and forgotten. Other times it was too much, with pages and pages of junk.
I highly recommend this book it's short, concise and to the point. It's...well...Just enough. :)