SAMPLE BUSINESS REQUIREMENTS DOCUMENT TEMPLATE
PRIORITY
Use the following priority table. It allows you to apply a ratings system to your
requirements, so you have the visibility (into the value, status, and description of each
requirement) that’s necessary for determining whether a particular requirement is
essential to project success:
The requirement is critical to the project’s success.
Without fulfilling this requirement, the project is not
The requirement is high priority re the project’s
success, but the project could still be implemented
in a minimum viable product (MVP) scenario.
The requirement is important to the project’s
success, as it provides value, but the project could
still be implemented in an MVP scenario.
The requirement is low priority (i.e., it would be nice
to have), but the project’s success is not dependent
The requirement is outside of the project’s scope
and is included as a possible component of a
prospective release and/or feature.
REQUIREMENTS CATEGORIES (RC1)
Detail the project’s functional use; break down your project’s requirements into categories so that they’re
easy to understand. You can duplicate this section for any successive project categories as needed. The
following table includes a unique ID for each requirement, the details of each requirement, the priority of
each requirement, and the name of the person who is driving or is responsible for the requirement.
SAMPLE TEXT: Increase the production of EV charging
units.
SAMPLE TEXT: Coordinate with manufacturing regarding
increases.
SAMPLE TEXT: Coordinate / align with operations.
SAMPLE TEXT: Obtain executive project approval / sign
off.