Task: Elicit Requirements

Identify the elicitation technique to be used for each Stakeholder

Use one of the elicitation techniques below:

Workshops: Workshops are facilitated meetings with multiple stakeholders.
Interviewing: Interviews are one-on-one meetings where the business analyst asks questions to draw out more information from the stakeholder.
Observation/Job Shadowing: Observation is when the business analyst watches the users performing their daily tasks and asks questions about their tasks or work. This technique gives you the advantage of actually seeing what users are doing at their work as opposed to what they tell you they are doing.

Schedule the requirements gathering meetings

Schedule meetings with stakeholders and set expectations ahead of time.

Elicit requirements

Ask probing questions.
Observe user’s daily tasks.
Repeat back to the Stakeholder to ensure you have captured the information accurately.
Identify areas that the Stakeholder or User has categorized as “pain points”.
Gain an understanding of policies and procedures that may be used to define business rules.

Document the requirements

Define functional and non-functional requirements.
Identify business rules.
Record them into the Business Requirements Document template. Save the BRD and name it abiding by the naming guidelines.
Develop use cases. Save the use case and name it abiding by the naming guidelines.
Upload the BRD and use case to the project’s SharePoint site.