Business Requirements

Project: [Your project name]

Problem Statement

💡 Tip: This is assessment of the current state of the issue. Include how you identified the issue and quantify whenever possible.

Ideal Future State

💡 Tip: This should answer the question: “What should be happening?”

Current State / Data

💡 Tip: This should help answer the question: “What are we doing instead?” Use data and specific business examples to make your case. Link any relevant documents or reports that can support your case.

Success Criteria & ROI

💡 Tip: This should answer the question "How will we measure success?”

Functional Requirements

💡 Tip: This should answer: “How will we solve this problem?” Work with your technical partner to fill this out. This is a good chance to hear from others why they would recommend a certain approach vs. telling them how to solve something. Think about the technical specs, potential EPD/BizTech constraints, data dependencies, existing systems and processes, workflows, etc.

Approach / Phases / Timeline / Key Dates

💡 Tip: Think critically about timing and sequencing. What are the major dependencies, callout whenever possible.

Type

Due Date

Owners

Dependencies

Type

Due Date

Owners

Dependencies

1

Event / activity / deliverable

5/19/20

​

2

​

​

​

3

​

​

​

There are no rows in this table

⁠

Alternatives

💡 Tip: Alternatives should be feasible — they should be realistic; diverse — they should not all be micro-variants of the same situation; and comprehensive — they should cover the problem space. Always consider that NOT doing something is an alternative, and the justification for that is often opportunity cost / resource competition: there might be something else we should be focusing on that is outside the problem space being discussed.

Other

💡 Tip: Include competitor examples, sample screenshots, process map, sketches, whiteboarding, etc.