Business requirements gathering is the first step in creating “As Is” and “Future” states.
Often, BRG is combined with standard operation procedures and practices (SOP)—but all too often, BRG is not documented very well—leading to poor solution choices. For your software evaluation, BRG provides the framework for your SOP. When preparing for an enterprise software selection your organization must assess its current state and where you may want to go. BRG is the first step in creating the “As Is” and “Future” state for a functional and technical SOP document.
Business Requirements Gathering Methodology
Let’s talk about BRG best practices. When creating business requirements documents there are several approaches to gathering the information, documenting in a structured methodology, definition and prioritization of current and future needs and differentiation between needs and wants are several areas to focus on. These components encourage accuracy and ensure a complete and balanced document for organizations to present to vendors in an RFx or purchase process.
Vendors then conduct their business process mapping to match their features/functions to your organization’s specific practices and configure the system to maximize your organizational processes. Take advantage of RequirementsHub to expertly create and manage your requirements project.
Requirements Gathering Techniques
The following is an approach describing how to create a proper structure for gathering corporate business requirements. This structure provides a framework that can be replicated for each business process.
There are several dozen methods and frameworks to gather business requirements such as TOGAF, ZACHMAN FRAMEWORK, AGILE etc. Since most of them pertain to building products we will stick to techniques that can be used to solicit business requirements within an enterprise software selection process. The key outcome in this exercise to fully document every step of a workflow, business process and task. This attention to detail will simplify the RFX process later and also assist the vendor in proper and optimal system configuration once a software is selected.
Several methods of gathering business requirements are:
- Focus Groups within the company – a group of users that perform specific duties and tasks that can be polled to ascertain their duties, functions and system interactions within the company.
- Interviews – an account of what is currently being done to support the business
- Interface Analysis – an examination as to inputs, outputs and intermediary steps that may be required for the system to function and define interoperability to existing systems
- Surveys – an internal account from different points of view as to how operations and processes actually happen
- Observation – this is refers to walking around and drawing your own conclusions as to how things are done
Business Requirements Gathering Methodology Framework
The graphic represents all of the components to include when creating the BRG document. Each piece is defined below.[/vc_column_text][/vc_column][/vc_row]
The following two examples apply to gathering requirements for a BI system or ERP system. Note the top business process, the tasks and criterion within the process and how it applies to the overall workflow. Criterion are individual short sentences that define needs and wants. [/vc_column_text][/vc_column][/vc_row]