User Story Template

Summary of requirement

Summary of the reason for the story

Documentation

Domain Changes

Confluence Pages

Requirement

As a User I want to be able to ...

Action

When the User selects ... he gets ...

Touch Points

Parts of the system which are affected by this

Acceptance criteria

• Scenario 1 - Select A ....

• Scenario 2 - Select B ...

• Scenario 3 - Select C ...

User Notification

Communication to users of

• success

• unexpected errors

User Validation

Validation which the user needs to know about

System Validation

Validation stopping a process from working properly

Fallback Case

When something goes wrong which is not thought about, or is uncontrolled, what happens?

Is it a catastrophic error - if so what should be done - should the user be able to continue?

UI Design

Checklist below should be reviewed before any estimating activities!

If more than 3 items checked, ensure the story scope is not too big.

1. Requires frontend development. Which pages/components?

2. Requires backend development. Which services?

3. Requires Web API changes. Which endpoints?

4. Requires infrastructure maintenance. Which resources? Note: include terraform.

5. Requires new service(s) (repository, pipelines). Service name(s)? Note: ensure ticket is created and assigned to Sergey.

6. Requires Seko 360 integrations. Which applications?

7. Requires 3rd party systems integrations. Was integration information provided?

8. Requires any validations?