From the course: Business Analysis for Project Managers

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Eliciting requirements

Eliciting requirements

- Hopefully you know this, but just in case, let me say it for the record. Never trust the first documentation you see. Documentation has a terrible reputation for being outdated, irrelevant, or inaccessible. So you have to vet it. It's like looking something up on the internet these days. You need to search intentionally. Triangulate your findings, check your sources, because the last thing you want is to do work to satisfy an irrelevant requirement. As a PM, you're probably familiar with collecting requirements and using data gathering techniques. But BAs refer to these activities as elicitation. When we say elicitation, we mean the activity of drawing out information from stakeholders and other sources. Usually, the initial elicitation is done during the needs assessment activities, and then you do additional discovery once the project gets going. During elicitation we check out documents, yes. But we also talk to…

Contents