Skip to content

Evolve

Requirement Sheet and Acceptance Criteria

Markdown sheet to request a software improvement with problem, users, scenarios, rules, acceptance criteria in Given-When-Then format, constraints, out-of-scope items and change log.

In this guide
Definition of a software improvement from the problem to its acceptance test.

How to use it

Fill one sheet per improvement and review it with the developer before starting. What you cannot answer is an open question to resolve.

Bring it to your business

Download resource
# Requirement sheet and acceptance criteria

**How to use it:** one sheet per improvement. Fill problem, users and scenarios first. Complete rules and acceptance with the developer. Do not include passwords or real personal data.

Improvement: ____________  Requested by: ______  Date: ______  Version: ___

## 1. Problem
What happens today (with a recent example): ______________________

## 2. Users
- Who experiences the problem: ______
- Who will use the improvement: ______

## 3. Scenarios
| # | Situation | Type (normal/exception) |
|---|---|---|
| 1 | | |
| 2 | | |

## 4. Business rules
- 

## 5. Acceptance criteria
| # | Given… | When… | Then… |
|---|---|---|---|
| 1 | | | |

## 6. Constraints
- 

## 7. Out of scope
- 

## 8. Change log
| Date | Change | Effect on effort or date | Approved by |
|---|---|---|---|
| | | | |

## Approval
- [ ] Reviewed by requestor
- [ ] Reviewed by developer

## Synthetic example (delete before use)
| # | Given… | When… | Then… |
|---|---|---|---|
| 1 | an order exceeds COP 5.000.000 | it is confirmed | an email is sent to the sales manager with number, customer and amount |
| 2 | the order is canceled | a notice has already been sent | a second email is sent informing the cancellation |
Authorship and sources

Author: RealStack Team