Acceptance and change requests

Customer acceptance

Who can use it: client users.

A Validated feature is waiting for the client. The client’s acceptance is the last step.

Use case

REQ-4 is Validated. Tom opens it, selects See the test results, checks Lena’s screenshots for each criterion, and accepts. REQ-4 is now Customer accepted: done, and read-only from here on.

1. Open the validated feature.
2. Select See the test results to review each test case and its screenshots.
3. Accept the feature.

Change requests

Who can use it: Project Managers, Super Admins and client users.

Once a feature is delivered (Validated or Customer accepted), its requirement can’t change. To change it, raise a change request: a new feature that holds only the change.

Use case

A month after launch, Tom wants customers to choose the delivery slot when reordering. Tom raises a change request from REQ-4. It becomes REQ-15, “Change request of REQ-4”. It holds only the new story, while REQ-4’s stories show read-only for reference. REQ-15 goes through the normal steps, and REQ-4 is never modified.

flowchart TD
    R4["REQ-4 · Reorder a past order<br/>Customer accepted"] --> R15["REQ-15 · Change request of REQ-4<br/>choose a delivery slot"]
    R4 --> R18["REQ-18 · Change request of REQ-4<br/>reorder from favourites"]
    R15 --> R21["REQ-21 · Change request of REQ-15"]

1. Open the delivered feature and raise a change request.
2. Write only the change: new or changed stories and criteria.
3. It follows the normal journey: sign-off, spec, tasks, tests, acceptance.

Note

A feature can have several change requests, and a change request can have its own. The Change Requests tab on a feature lists them.