Project Management

Please login or join to subscribe to this thread

What are the best practices for gathering requirements and building a BRD document for custom off-the-shelf products

linkedin twitter facebook   Business Analysis   Consulting   Scope Management  
avatar
Anonymous
test
Sort By:
avatar
Keith Novak Tukwila, Wa, United States
If a product is off-the-shelf, then it is not custom.
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
I am also confused, if the product is off the shelf then it is not custom so please clarify. Thanks!
avatar
Md. Golam Rob Talukdar
Community Champion
Project Manager| AWR Development (BD) Ltd. Cox's Bazer , Bangladesh
* Gather Requirements: Conduct interviews, workshops, and surveys with stakeholders to understand their needs, pain points, and expectations for the COTS product customization.
* Analyze the COTS Product: Thoroughly examine the COTS product's features, functionalities, limitations, and customization options to determine if it aligns with your requirements.
* Prioritize Requirements: Evaluate the importance and urgency of each requirement to ensure the BRD focuses on essential features.
* Document Everything: Clearly document all requirements in the BRD, including functional and non-functional requirements, user stories, and acceptance criteria.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Creating a BRD when a COTS application has already been predetermined is a waste of effort unless there is an expectation of significant customization or integration with other systems, in which case the requirements should focus on the customized or developed aspects. Otherwise, you are effectively regurgitating the user manual...

Kiron
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Take a closer look to business analysis related documentation in the PMI, practice guide and BOK.
avatar
Giorgos Sioutzos Senior Business Analyst| Netcompany Athens,, Greece
Elicitation is not just gathering requirements. It’s about understanding and many times providing additional meaning and restructuring the information that is communicated. Performing this task effectively means you are able to figure out the real business needs and to guide the stakeholders to reveal the real their actual aspiration about the future state.

Many factors can define the best practices given the context:

- Stakeholders needs and characteristics (maturity, knoweldge etc.)
- Project related considerations (time, budget, project life cycle etc.)
- How familiar and experienced is a business analyst with a specific technique
- Organizational standards

Business analysts should show judgment when choosing one technique or blending.
avatar
FAIZA KHALIL MIS,Policy & Project Coordinator| SAMBA BANK Karachi, Sd, Pakistan

Engage stakeholders early, analyze COTS features, and conduct fit-gap analysis. Use workshops and interviews to capture clear requirements. Prioritize business-critical needs, validate iteratively, and maintain traceability to ensure alignment between business goals, product capabilities, and minimal customization for successful delivery.

Please login or join to reply

Content ID:
ADVERTISEMENTS

It's like deja vu all over again.

- Yogi Berra

ADVERTISEMENT

Sponsors