Photo credit: Jacob Botter
Requirements elicitation is one of the many must-have skills that successful business analysts have in their tool kits. But it’s hard to know when and if your requirements elicitation activities are truly complete.
As you get into the nitty-gritty of a project, and you find that you’re missing an important requirement, that’s when you might have to go back to the drawing board.
And there’s nothing worse than starting from scratch when you’ve already invested time and energy into creating a comprehensive solution that positively impacts all stakeholders.
So how do you know the difference between eliciting enough requirements and falling short? This question is one of the many reasons I’ve developed my new 12-week course, Mastering Business Analysis Fundamentals, which delivers the necessary skillsets required for you to reach a senior BA position.
Requirements elicitation is part of that recipe for accelerated success in the ever-changing world of business analysis. To know that requirements elicitation is in fact complete, take the following action steps.
1. Consider the big picture.
Finances. Operations. Customers. There are more than a handful of factors that go into the solution you provide. As you ascertain whether or not you have the requirements you need, consider what the whole-picture outcome will be. If you shift through piece-by-piece, you may miss something vital.
2. Think of all the stakeholders.
Stakeholders aren’t just the people you have meetings with—and they’re not just the people you get requirements from. Think of everyone who has some stake in the work you’re doing. If you can’t satisfy all parties, then you need more requirements.
3. Remember the questions you asked during the interview process.
Hindsight is 20/20, so they say. As you move through the process of creating a solution to any number of problems, you’ll get stuck wondering why you’ve hit a particular snag. Think back to the questions you asked during the interview process, and you’ll figure out whether or not you need to ask more.
4. Put the end user into consideration.
The end user’s satisfaction is the measuring stick of the quality of your solution. It’s his feedback that matters. It’s her experience that weighs whether or not your performance worked for the greater good. Always keep the end users in mind, and if you find that there is a hole in their experience, then you need more requirements to get the job done.
Ready to NEVER have to worry about requirements elicitation?