Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Driving requirements when the solution may already be known
Previous Previous
Next Next
New Post 2/14/2018 8:32 AM
User is offline anthonyswope
1 posts
No Ranking

Driving requirements when the solution may already be known 

I was talking with my Director yesterday about solution based requirements.  What we are ultimately trying to do is have a good understanding of what the requirements elicitation process may look like what a solution is known.

So the scenario that we put into place was, I need a fitbit.  The fitbit is intended to solve a need/requirement.

We completed a role playing exercise where my Director acted as a stakeholder and I played the role of a BA.  The Director told me that she needed a fitbit.  I asked a few why questions before we finally nailed down the overall need which was, the stakeholder needed a solution that would motivate them to regularly exercise.  And the Director is wondering if this is a good scenario to use when interviewing new BAs and testing there technique and knowledge of identifying the requirement when a stakeholder may already have an idea in mind.  I would like to get some feedback from others.  I have been considering if there is a better scenario to use that will make driving the requirements elicitation once the solution has been identified by a stakeholder.


New Post 2/27/2018 9:23 PM
User is offline NessyCat
3 posts
No Ranking

Re: Driving requirements when the solution may already be known 

I am working on a similar project at the moment, where the end solution is already decided and I have to gather requirements to tailor the solution to the unique needs of the area, as far as possible whilst avoiding the need for customisation (a fine balancing act!).

To be honest, I haven't really done anything too far different from the normal BABOK methodology.  I couldn't gather a need as I came onto the project when it was already in full swing.  But I have been able to garner some of the issues they are having and I have collected as-is requirements and then work shopped to-be, system agnostic.

It is taking a little while but I think it's valuable because if you don't do this, you may miss requirements in the final solution because you didn't realise it was something they were currently doing.

Not the best situation to be in as a Business Analyst, but a common one.  I feel for you.

New Post 3/7/2018 10:36 PM
User is offline Nimil
2 posts
No Ranking

Re: Driving requirements when the solution may already be known 

Solution based requirement elicitation happens when your stakeholders are sure about the end state/goal. Stakeholders are very much sure of the business problem that the end state will resolve. In such a scenario, the primary objective of a BA is to gather requirements to understand how to achieve the end state.

First step is to understand the business problem. In your e.g., if  I need a Fitbit, why do I need it? What problem will it resolve? A BA should ask questions to identify if I need a Fitbit because all my friends have it or I need a fitbit to make sure I keep a track of my fitness activities or I need a Fitbit to ensure my motivation towards my health or something else.

Upon identification of the problem, next step is to identify the reasoning behind the solution. Why Fitbit? Why not Garmin or something else? Why only Fitbit can resolve the identify problem? Is it becasue the FitBit has more features or is it because of the cost or is it becasethats the only solution I know?

Upon identification of problem and the reasoning behind solution, a BA can then jot down the approach towards a given solution from a business problem. Start with questions like who is going to benefit out of this solution? Will you be wearing Fitbit whole day? If not how many hours? What are your primary hours? How long charging would be needed and so on and so forth.

Once approach is decided, start asking questions on solutions and design. Ultimately you'll figure out everything  a BA needs to.


When I interview a BA, I like to ask them what if you need to open a restaurant in a food court. How would you elicit requriements and how'll you identify the stakeholder's ask?


Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Driving requirements when the solution may already be known

Community Blog - Latest Posts

The software development industry requires productivity and performance to create a successful product and meet business objectives. That's why everyone in the software industry always looks for new ways to streamline their processes and create better software. Today's world is experiencing an increasing pervasiveness of artificial intellig...
In the dynamic landscape of business analysis, staying ahead of the curve is imperative for success. The role of a business analyst is pivotal in driving organizational growth and efficiency. To excel in this domain, one must harness the power of cutting-edge tools and adopt strategic approaches that streamline operations and enhance decision-makin...
Angular is a powerful open-source web application framework developed and maintained by Google. It is designed to simplify and streamline the process of building dynamic and interactive web applications.  Angular was first introduced in 2010 as "AngularJS" by Misko Hevery and Adam Abrons during their work on a project called "...


Upcoming Live Webinars


Copyright 2006-2023 by Modern Analyst Media LLC