SMART requirements
One useful acronym for defining requirements is SMART :
One useful acronym for defining requirements is SMART :
Specific : A goal or requirement must be specific. It should be worded in definite terms that do not offer any ambiguity in interpretation. It should also be concise and avoid extraneous information.
Measurable : A requirement must have a measurable outcome, otherwise you will not be able to determine when you have delivered it.
Achievable : A requirement or task should be achievable, there is no point in setting requirements that cannot realistically be achieved.
Relevant: Requirements specifications often contain more information than is strictly necessary which complicates documentation. Be concise and coherent.
Time Bound: In order to be of value requirements must be completed within a defined time frame. As well as T stands for testable. You must be able to prove that the requirement has been satisfied. Requirements which are not testable can leave the project in limbo with no proof of delivery.
No comments:
Post a Comment