Business Requirements Flashcards
What does BRD stand for?
Business Requirements Document
What is a BRD?
A Business Requirements Document. It compiles all the business requirements of a product into a single document.
What does a BRD specifically focus on?
What NEEDs to be accomplished rather than how to accomplish it.
What does a basic business requirements document typically contain?
- Executive Summary
- Business Objectives
- Scope
- Functional Requirements
- Delivery Schedule
What is an Executive Summary?
A one-page document that sums up the goals and the mission statement of the business.
What are Business Objectives?
S.M.A.R.T (Specific, Measurable, Actionable, Realistic, and Time-based) goals that define the objectives of the business.
What does S.M.A.R.T stand for?
Specific, Measurable, Actionable, Realistic, and Time-based
What is a Scope?
The product specifications( what it is you’re building).
What are Functional Requirements?
The specific structure behind the product (user requirements, flowcharts, technical information, etc.).
Because BRDs aren’t technical documents, try to stay fairly high-level so that the general requirements can be understood and discussed without the nitty-gritty details.
What is a Delivery Schedule?
Deadlines and milestones for the project.
What is Backwards Scheduling?
This means rather than planning chronologically from start to finish, you begin by looking at the end date and planning backwards, calculating the time needed for every stage.
(It’s always a good idea to allow some bugger time to ensure that, even in an emergency, you can meet the deadline.)
What is extremely necessary to conduct before filling out a BRD?
Conducting a stakeholder interview- 1-on-1 discussions with key stakeholders.
What is a Stakeholder?
Any individual who may affect or be affected by decisions made during a project.
Stakeholders on a project may include: >The customers or users of the product or service >The client (if we have one) we're creating the product for) >The senior management team: CEO, CTO, COO, etc. >Product owners/managers >Business managers >Marketing team >Sales team >Content strategists >Web developers >Designers >Customer service team
(This list is by no means inclusive of all the individuals who could potentially be stakeholders in your project)
What are the two things to watch out for when conducting stakeholder interviews?
Presumed constraints and Jumping to solutions
What are presumed constraints?
Hindrances a stakeholder has in their mind that may or may not be necessary. To get to the root of it, ask them to explain why a particular constraint exists.
