Features and requirements

Who can use it: Project Managers, Super Admins and client users write features. Everyone on the project can read and comment.

A feature is one piece of work delivered on its own, numbered per project (REQ-1, REQ-2, …). Its requirement says what it must do. Everything that follows (spec, tasks, tests) traces back to it.

Use case

Tom tells Ravi that customers want to repeat last week’s shop. Ravi creates REQ-4 Reorder a past order, writes the description, and adds two stories with three acceptance criteria. Tom adds a screenshot of a competitor’s reorder button to AC2. Both sign off, and the requirement is frozen.

What a requirement looks like

flowchart TD
    F["REQ-4 · Reorder a past order<br/>description"] --> S1["S1 · See my past orders"]
    F --> S2["S2 · Reorder in one tap"]
    S1 --> A1["AC1 · Last 20 orders, newest first"]
    S2 --> A2["AC2 · Available items go to the cart"]
    S2 --> A3["AC3 · Unavailable items listed with a note"]

• User stories (S1, S2, …) say who needs something and why.
• Acceptance criteria (AC1, AC2, …) are the checks that prove a story works. Each one becomes at least one test case, and tasks link to the criteria they deliver.

Write criteria you can test

“Reorder is fast” can’t be tested. “Reorder adds every available item to the cart” can.

Write the requirement

1. Go to Features and select New feature.
2. Write the description in Markdown: the why and the context.
3. Add user stories, and under each story its acceptance criteria.
4. Add images to the feature, a story or a criterion where a picture helps.
5. Save. Every save is kept on the History tab.

Sign off: both sides

sequenceDiagram
    participant Ravi as Ravi (PM)
    participant Tom as Tom (client)
    Ravi->>Ravi: Draft REQ-4
    Ravi->>Tom: Submit for review
    Tom-->>Ravi: Request changes: "add AC3"
    Ravi->>Tom: Update and submit again
    Tom-->>Ravi: Sign off
    Ravi-->>Tom: Sign off
    Note over Ravi,Tom: Requirement signed off and frozen

1. Submit the feature for review.
2. A Project Manager and a client user both sign off. Either can request changes, which sends the feature back to draft.
3. Once both have signed, the requirement is frozen.

Caution

Sign-off waits until all five Business project docs are signed off.

Need to change a signed-off requirement?

When	What to do
Before delivery	Discard the feature (it stays readable) and clone it. The clone is a new draft with the same stories and criteria under the next key.
After delivery	Raise a change request.

Organise the list

• Priority: High, Medium or Low, then sort and filter.
• Modules: tag features by product area and filter by module.
• Search by key or title, and filter by status.