User Story Template

In theory, user stories are basically product features, requirements or tasks that add value to the end customer.
In practice, most Agile Teams use user stories as tasks that reflect what they are trying to accomplish, which of course is direct

In theory they should be written like this:

As a <user> (who) I want to… <what> so that… <why>
Example: As a front end developer I need to ensure the app is responsive so that it can work on different screen sizes

But using the format above to write user stories, requires more effort and space (which is limited if you're using post-it notes).

In practice, most Agile Teams write user stories as short tasks which start with a verb
<verb> and the task that is being performed (written in a short and concise manner)
Example: Ensure the app is responsive so that it can work on different screen sizes

Examples of verbs to start a user story would be:

Create
Develop
Build
Plan
Research
Perform
Test
and so on
e end customer.
plish, which of course is directed to meeting a customer need or requirement.

different screen sizes

d if you're using post-it notes). Plus it can get a bit repetitive and redundant, so…
Velocity Chart Template

Velocity = Total Story Points Delivered over a Sprint

The example below illustrates a basic example of a 4 Sprint Project. Being the Sprints in this case 2 weeks long this is a 2 mont
It has 15 user stories in total. I've used the name "User Story #" in the essence of time, but you would of course write the actu
Assumption: The team discards the user stories which aren't delivered since after discussion they don't consider required any

Sprint 1 Story Points

User Story 6 3 Note: this user story wasn't delivered in Sprint 1 since the tea
User Story 11 3
User Story 2 5
User Story 8 1
Total 12 Velocity Sprint 1 9

Sprint 2
User Story 1 5
User Story 13 1
User Story 5 1
Total 7 Velocity Sprint 2 7

Sprint 3
User Story 3 5
User Story 4 3
User Story 15 1
Total 9 Velocity Sprint 3 9

Sprint 4
User Story 9 3 Note: this user story wasn't delivered in Sprint 4 since the tea
User Story 7 5
User Story 14 3
User Story 10 1
User Story 12 1
Total 13 Velocity Sprint 4 10

Total Story Points 41 Average Velocity 9 Which means that on average the team
This is an indication of execution that al

Velocity Chart
Sprint Velocity Velocity Chart
1 9
2 7
10
9 9

7
locity
 Velocity Chart

10
3 9 9 9
4 10
7

Velocity
1 2 3 4
Sprint
e 2 weeks long this is a 2 month project.
would of course write the actual user story using the format described in the other tab
y don't consider required any longer. Keep in mind, that if they were required they would be added to another Sprint

vered in Sprint 1 since the team didn't have time to complete it

vered in Sprint 4 since the team didn't have time to complete it

eans that on average the team is delivering 9 story points per Sprint. This is known as the project's Velocity
indication of execution that allows for future planning and workload management.

10
9
 10
9

3 4
Velocity Chart Template

Velocity = Total Story Points Delivered over a Sprint

The example below illustrates a basic example of a 4 Sprint Project. Being the Sprints in this case 2 weeks long this is a 2 mont
It has 15 user stories in total. I've used the name "User Story #" in the essence of time, but you would of course write the actu
Assumption: The team discards the user stories which aren't delivered since after discussion they don't consider required any

Sprint 1 Story Points

User Story 6 3 Note: this user story wasn't delivered in Sprint 1 since the tea
User Story 11 3
User Story 2 5
User Story 8 1
Total 12 Velocity Sprint 1 9

Sprint 2
User Story 1 5
User Story 13 1
User Story 5 1
Total 7 Velocity Sprint 2 7

Sprint 3
User Story 3 5
User Story 4 3
User Story 15 1
Total 9 Velocity Sprint 3 9

Sprint 4
User Story 9 3 Note: this user story wasn't delivered in Sprint 4 since the tea
User Story 7 5
User Story 14 3
User Story 10 1
User Story 12 1
Total 13 Velocity Sprint 4 10

Total Story Points 41 Average Velocity 9 Which means that on average the team
This is an indication of execution that al

Traditional
Burndown Chart
Sprint Remaining Story Points
1 41 Burndown Chart
2 32
41
ry Points

32
 Burndown Chart
3 25
41
4 16

Remaining Story Points

5 6 32

25

16

6
1 2 3 4 5
Sprint

Another option
Burndown Chart
Sprint Remaining Story Points Delivered
1 41 9 Burndown Chart
2 32 7
3 25 9
4 16 10 9
5 6 0
Story Points

7
9
41 10
32
25
16 0
6
1 2 3 4 5
Sprint

Remaining Delivered

Another option
Burndown Chart
Sprint Remaining Story Points Delivered
1 41 9 Burndown Chart
2 32 7
3 25 9
41
4 16 10
5 6 0 32
Story Points

25

16
9 9 10
7 6
 41

32

Story Points
25

16
9 9 10
7 6
1 2 3 4
Sprint

Remaining Delivered
e 2 weeks long this is a 2 month project.
would of course write the actual user story using the format described in the other tab
y don't consider required any longer. Keep in mind, that if they were required they would be added to another Sprint

vered in Sprint 1 since the team didn't have time to complete it

vered in Sprint 4 since the team didn't have time to complete it

eans that on average the team is delivering 9 story points per Sprint. This is known as the project's Velocity
indication of execution that allows for future planning and workload management.

n Chart
n Chart

25

16

6
3 4 5
print

n Chart

9
10
25
16 0
6
3 4 5
print

Delivered

n Chart

16
9 10
6 0
 16
9 10
6 0
3 4 5
print

Delivered