The contractor at my company who is leading a project to define our Product Development Process, has just published a document which requires that the following attributes be listed for each requirement in a Requirements Document:
Priority - Mandatory, Highly Desireable, Optional
Stability - Probability the requirement will change over time - 100%, 75%, 50%, 25%, 0%
Risk - Probability that lack of implementing the requirement will have an adverse impact on the project - 100%, 75%, 50%, 25%, 0%
Effort - Effort required to meet the needs expressed in the requirement - Expressed in terms of person-weeks of work
Seems like a bit of overkill to me. Especially since my company is just learning about requirements in general. Thoughts? Are any of you listing this many different attributes for each requirement? I would guess mainly the people in regulated industries.
Re: Requirement Attributes - How many is too many?
Yeah for those working in regulated industries requirements management is extremely important as traceability and impact analysis etc is in itself an essential requirement.
This often is not as essential on smaller projects where the cost and impact of requirements changes is not so important, however i was surprised when i started working for my present company just how much it helps to manage your requirements well.
Not trying to give you the hard sell here but sounds like some training in requirements management and a good tool to manage this would be helpful?
We offer a product called DOORS and our professional services division supply training in both requirements management and obviously in the product itself.