In one of the Carnivals of Business Analysts the theme was “Requirements Analysis."
I searched the web far and wide and came up with a number of blog posts and articles on Requirements Analysis. I felt that it missed something practical and directly on how to analyse the requirements you have gone out and collected, After all, if you are just going and collecting information and then passing it onto the development team you are a waiter, not a business analyst.
The most trying projects are those where the business plays the role of solutions architect, and the BA plays the role of “waiter”. - Jonathan Babcock
So I wrote an article myself highlighting seven analysis techniques that can be applied to requirements. You’ll analyse and apply attributes to them between getting them raw off the business and handing the to the solutions team.
Many of these techniques will be familiar to you. A few may be new to you. All have been around for several years. You might find some of my assessments and comments vague, incomplete or wrong. If you do, can you be a good stakeholder and let me know what you think I should do to improve things?
The full article is here.