Christine M. Robiso
Christine M. Robiso
Christine M. Robiso
ROBISO
The Business Analyst’s first responsibility is to gather requirements from the client. The key
question that emerges now is how do they collect requirements from the client? A BA may use a variety
of effective techniques to gather requirements. This include, Brainstorming, Document analysis, Focus
navigation flow, paper prototyping, screen flows), Requirements workshops and Survey/questionnaire.
stakeholders, users, and customers to be applied to the design of the initiative or the solution. During
this phase, strong organizational and communication skills are required, as it is generally up to the BA to
shape the information into models, diagrams, and other tools to communicate the findings to decision
makers and team members. Effective requirements elicitation is a critical component of project success.
Ironically, it is a process that many analysts overlook. This oversight can be costly to the project in terms
of time and money, but it can also result in incomplete requirements or, worse, a failed project.
Is elicitation necessary? The answer is unequivocally YES. Based on this example, “a Standish
Group report identifies “incomplete requirements” as the leading cause of software project failure, with
poor requirements accounting for 50% of project failures. Poor requirements are the result of poor
elicitation, which can also result in scope creep, budget overruns, and insufficient process redesign.”
Therefore, elicitation is important because many stakeholders are unable to articulate the
business problem accurately. As a result, business analysts conducting the elicitation must ensure that
the requirements generated are clearly understandable, useful, and relevant. A well-defined problem
and clear requirements will help to create the right solution that adds value to the business.