Studies have proven time and again that poorly defined requirements have a direct impact on project failure. Poorly defined requirements include the following amongst other things:
- Requirements do not represent the actual needs of the customer
- Requirements are incomplete or conflicting
- Requirements are not written concisely and clearly
In this article, The Skilled Business Analyst discusses guidelines which Business Analysts can use to develop quality requirements.
- Concise – make sure your requirements are to the point. Use plain English and remember quality over quantity.
- Consistent – if you are using matrices and models to support your requirements, ensure they are not conflicting and they are telling the same story.
- Testable – ensure you will be to verify each requirement once implemented
- Prioritized – your requirements must be ranked in order of importance and value.
- Complete – your requirements must not be open to misinterpretation and must not leave a reader to make assumptions
- Feasible – your requirements must be within the boundaries of the project timelines, cost and scope.
- Atomic – your requirements must be broken down to the lowest level of detail
If you are interest in learning more about writing quality requirements contact The Skilled Business Analyst today to discuss how we can help you take your career to the next level!
Yours in Analysis
Tendai
Business Analysis Instructor