Business Requirements Document
Business Requirements Document (BRD)
Business requirements are the critical activities of an enterprise that must be performed to meet the organizational objective(s). The BRD should remain solution independent. In the context of the project scoping for hardware procurement and installation, this is about identifying and documenting the business requirements of customers, employees, and vendors early in the development cycle to guide the design of the future state. Business requirements are captured by analyzing the current business activities and processes of the as-is state (current process) and defining a target state (to-be process) that will deliver the planned business outcomes that contribute to the organizational objectives.
Objectives of the BRD:
Stakeholders
to gain agreement with stakeholders about what will and will not be delivered
Vendors
to provide a foundation to communicate to a vendor (or in-house provider) what the solution needs to do to satisfy the customer’s and business’ needs
Sponsors
to provide input into the business case development phase of the project
Customers
to describe ‘what’ (not ‘how’) the customer/business needs will be met by the proposed solution
Business Requirements Document (BRD) describes the high level requirements that senior management would understand, for example, SS relationship:
The BRD is the foundation for all subsequent project deliverables, describing what inputs and outputs are associated with each process function. The BRD describes what the system would look like from a business perspective, distinguishing between the business solution and the technical solution. Business requirements often include: business context, scope, and background, including reasons for change key business stakeholders that have specific requirements success factors for a future/target state constraints imposed by the business processes or other systems business process models and analysis defining either 'as-is' and 'to-be'
Business requirements are the critical activities of an enterprise that must be performed to meet the organizational objective(s). The BRD should remain solution independent. In the context of the project scoping for hardware procurement and installation, this is about identifying and documenting the business requirements of customers, employees, and vendors early in the development cycle to guide the design of the future state. Business requirements are captured by analyzing the current business activities and processes of the as-is state (current process) and defining a target state (to-be process) that will deliver the planned business outcomes that contribute to the organizational objectives.
Objectives of the BRD:
Stakeholders
to gain agreement with stakeholders about what will and will not be delivered
Vendors
to provide a foundation to communicate to a vendor (or in-house provider) what the solution needs to do to satisfy the customer’s and business’ needs
Sponsors
to provide input into the business case development phase of the project
Customers
to describe ‘what’ (not ‘how’) the customer/business needs will be met by the proposed solution
Business Requirements Document (BRD) describes the high level requirements that senior management would understand, for example, SS relationship:
The BRD is the foundation for all subsequent project deliverables, describing what inputs and outputs are associated with each process function. The BRD describes what the system would look like from a business perspective, distinguishing between the business solution and the technical solution. Business requirements often include: business context, scope, and background, including reasons for change key business stakeholders that have specific requirements success factors for a future/target state constraints imposed by the business processes or other systems business process models and analysis defining either 'as-is' and 'to-be'