BRD Flashcards
Components of BRD
Executive Summary: A one-page document that sums up the goals and the mission statement of the business.
Business Objectives: S.M.A.R.T. (Specific, Measurable, Actionable, Realistic, and Time-based) goals that define the objectives of the business.
Scope: The product specifications—in other words, what it is you’re building. It’s good practice to err on the side of more detail here since disputes between stakeholders during design and development can cost both time and money.
Functional Requirements: The specific structure behind the product (user requirements, flowcharts, technical information, etc.). Since the BRD isn’t a technical document, try to stay fairly high-level so that the general requirements can be understood and discussed without the nitty-gritty details.
Delivery Schedule: Deadlines and milestones for the project. Backwards scheduling is a helpful way to ensure you meet the delivery schedule. 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 buffer time to ensure that, even in an emergency, you can meet the deadline.
Questions for interviews?
What’s your role in this project?
What do you think this product is going to be?
Who do you think this product is for?
When is the version we’re designing going to be released?
What worries you about this project? What’s the worst thing that could happen?
What should this project accomplish for the business?
How will you, personally, define success for this project?
