In the previous series of posts I introduced my favorite requirements elicitation technique, “Business Event/Response”. Of course there are many other techniques which can act either as complementary to or in place of “Business Event/Response”. The techniques you choose depend on many factors including the type of project, knowledge depth of the Subject Matter Experts (SME), the availability of documentation, time constraints, etc.
A skilled Project Manager that is also a seasoned Business Analyst (BA) is a very valuable commodity. I encourage all PM’s to increase their BA ability by reading books, attending webinars and seminars, and putting their new knowledge to practice. There is no substitute for actual work experience in this realm.
Here are the topics I will address in this series of upcoming posts:
- 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
- Part 14 – Summary
A reminder that my Kindle book “Project Management For The Real World” is available at
Practical Project Management Tips and Tools 