<aside> 💡 Use this template, if more detailed documentation, such as a Business Requirements Document (BRD) is needed. Typically, BRD documents are required by a PMO for stricter project governance and compliance.

Think of this as an expanded version of your Epics in the Product Backlog. You need to work with a user-facing stakeholder who has the ultimate product knowledge to describe requirements and define its priority, which typically is the Product Owner.

</aside>

Project Name: Hybrid Project Management

Author: Product Owner Version: 1.1 Status: Approved

Date: July 31, 2022

Approved by:

• [ ] Name, Project Sponsor
• [ ] Name, Business Sponsor
• [ ] Name, Business Sponsor

Overview

<aside> 💡 Provide a brief project introduction and documentation purpose.

</aside>

The Hybrid Project Management using Waterfall and Agile project aims to establish an end-to-end process supplemented with tools to guide users on how to implement based on a hybrid method.

This Business Requirements document is used to define high-level project deliverables which could be functionalities, hardware, data, integration, or compliance requirements. This is necessary to define and bound the project scope.

Assumptions

<aside> 💡 Mention any key assumptions necessary to implement the project.

</aside>

1. Users are limited to full-time staff in the USA and Canada
2. A Pilot Release will be conducted first to Sales and Marketing before rolling out to all staff.

Requirements

Business Requirements

Untitled Database

Functional Requirements

<aside> 💡 Functional requirements are features, user interface, or user experience-related items.

</aside>

Functional Requirements Database

Use Cases

<aside> 💡 Tie Use Cases with Functional Requirements to show a step-by-step description of how the system will be used to achieve an outcome.

</aside>