Agile & Traditional Requirements (4 Similarities)


There is often a lot of talk around how different Agile is from traditional methodologies, but this isn’t always the case. Let’s take a look at where some similarities can be found.


1. Expression of Business Need

When it boils down to it both approaches have the same goal for their requirements — to develop a good quality product or solution that meets the business needs.  To do this you must:

  • Focus on the business vision and the objective of each increment
  • Make the business vision and the objective of each increment clearly visible to all
  • Figure out what is important for each business need, it might not be what you (or the business) first think.


2. Need to be clear, concise and unambiguous

Well written User Stories need to be clear, concise and complete.  Double check against this checklist:

  • Is it a single requirement or does it over lap?
  • Is it easy to read and understand by non technical people?
  • Is it unambiguous and not susceptible to different interpretations?
  • Does it contain definitions or descriptions?  If so remove them.


3. Do not constrain design

It is important for all requirements not to suggest or contain a solution.  But they must also not constrain the solution either.  This is the same for Agile requirements too, they should avoid being tied to a particular solution for as long as possible.


4. Need to be testable

A testable requirement is a requirement that has been broken down to a level where it is precise, unambiguous, and in an absolute state.  For most requirements, they can be tested by:

  • Inspection
  • Aanalysis
  • Demonstration


Our easy to follow online course which provides a structured overview of business analysis and what it takes to become an excellent Business Analyst. Perfect for Entry Level BAs, Career Changers or for anyone interested in Business Analysis. It’s also great refresher course for Experienced BAs.

Ba Simplified