Epics
Epics describe the high-level requirements that are slated to be completed for this project. Epics are further broken down into stories which can be completed within one sprint.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Stories
Stories describe the more granular level requirements which can be completed within one sprint.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
User Story Map
The user story map shows the journey a user will take when performing tasks within the web application.
Read the story map from top down and left to right. The major activities are listed on top, broken down into tasks, then sub-tasks.
Each sub-task is categorized into one of three values:
Delighter = functionality a customer would be happily surprised to see. These can be thought of as differentiators.
Satisfier = the more of this type of functionality, the happier they will be.
Basics = the customer expects to see this type of functionality. If it is NOT included, the customer’s dissatisfaction with the solution increases.
| Iframe | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...