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.

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?