In the prior posts in this series, I introduced the following requirements elicitation techniques:
- Part 1 – Overview
- Part 2 – Acceptance Criteria
- Part 3 – Benchmarking
- Part 4 – Business Rules Analysis
- Part 5 – Data Modeling
- Part 6 – Document Analysis
- Part 7 – Interviews
- Part 8 – Non-functional Requirements
- Part 9 – Observation
- Part 10 – Prototyping
- Part 11 – Root Cause Analysis
- Part 12 – Surveys and Questionnaires
- Part 13 – SWOT Analysis
These are in addition to the Business Event/Response technique which I discussed in detail in a prior series of posts. These techniques can be considered a “toolbox” from which you can select the appropriate tools for the job. You will likely never use all of these in a single project. Based on the type of project you are working on, you will select the techniques that fit the size, background and scope of the project. Every Project Manager should have familiarity with these techniques and be able to apply them. They are core techniques in the Business Analyst’s Body of Knowledge (BABOK).
If you are a Project Manager and don’t currently perform the Business Analyst function, I encourage you to get training in this area. PM’s that can perform this function are immensely valuable to their organizations.
Feel free to leave comments on your own experiences as a Business Analyst. Include what worked well, what didn’t and why.
A reminder that my Kindle book “Project Management For The Real World” is available at