This presentation captures industry's best practices for requirement gathering in any field. It covers the do's and don'ts for business requirement gathering process. More content will be added for the tools to be used for it.

1. Name: Mansi Mehra
Title: Project Manager and Operations
Manager

2. A capability needed by a customer or user to
solve a problem or achieve an objective
A capability that must be met or possessed by a
system to satisfy a contract, standard,
specification, regulation, or other formally
imposed document.

3. Do’s in requirements gathering
Define and agree to the scope of project
Create precise and clear requirement document
Involve all the stakeholders from the beginning of
the project
Confirm your understanding of the requirement
with the client
Get a sign-off from the client on the requirements
Create a prototype if possible to demonstrate a
demo of the requirements

4. Don'ts in requirements gathering
Don’t assume what is required by the client
Don’t involve technology team or product team
until the requirements are set
Don’t decide the priority yourself but discuss it
with all the stakeholders
Don’t simply discuss the requirements and take to
the technology team. Write them and get a sign-off
from the client
Don’t write incomplete, ambiguous and not
verifiable requirements

5. www.mansimehra.com
mansi.mehra@gmail.com