Introduction: Use of the template

Planning Sheet:
1. In "Planning Sheet" "Colum "K" you must register "No. of Team member
Available hours of work (resources) in the Sprint is calculated.
This is used to compare with the total amount of hours you allocates to a
If you over allocates / estimates too many hours of work for the period, y
2. In Column "A" register Story ID / Task ID and describe Products and Task
3. Define No. of necessary Resources for each Task in Column "C"
4. Estimate each Task using Three Times Estimation (Value A, B, C) in Colum
The estimate must be based on how many clock hours is necessary for
The Weighted Average ("M") value in column "H" and Standard Deviation
If Standard Deviation > 10% of "Weighted Average", it's recommendable
(You will get a warning in column "J")
The "Total amount of work" for each task (Column "D") is calculated auto
5. The Values of "Total amount of work" in Column "D" is tranferred to the

Sprint Backlog Burndown

6. Every day at the Daily Sprint meeting The Team register - starting in Colu
If there haven't been done anything on a task, there's no registration, of
From the column where the registration is done and to the right (from c
The Burn Down Chart Sheet is updated automatically.

Burn Down Chart

Is a Graphical representation showing:
1. The linear path (the red graph) through the Sprint, based on the as
2. Compared to this graph the other graph (the blue graph) show how
(Effort left) in the Sprint Backlog Burndown Sheet is an essential tas
Story ID
Task ID

1
2

3
4
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 Sprint

Stories / Tasks

Define common Vocabulary

Define Common Structure and overall design requirements (UI etc)

Choose the area of the domain according to selected User Stories

Create a class diagram for the chosen domain
US 1 - For User Story - As a <user>, I want <goal> so that <reason> - Develop / Cre
- Sequence Diagram
- User Interface
- Non Functional Requirements
- Test Cases
- Functionality (Code)
- Tables in Database
- Test it – Approved / Done?
- Implement
US 2 - As a <system>, I want to <run a batch every evening at 9 PM> so I can <print a
- Sequence Diagram
- Non Functional Requirements
- Design Report Layout
- Test Case
- Functionality (Code) - SQL Report Builder Database
- Test it – Approved / Done?
- Implement
US 3 - For User Story - As a <user>, I want <goal> so that <reason> - Develop / Cre
 Effort "Day 0" calculated using three time estimates (or PERT

No. of
Total Read note i cells for calculations
team
amount
member
of work Estimate effort in hours
per task
A B C M Sd

4 8 2 2 2 2 0
4 24 6 6 6 6 0
0 0 0 0 0 0
4 8 2 2 2 2 0
4 12 2 3 4 3 0.4
0 0 0 0 0 0
1 3.3 2 3.5 4 3.3 0.4
1 2 1.5 2 2.5 2 0.2
1 2.5 2 2.5 3 2.5 0.2
1 2.9 2 3 3.5 2.9 0.3
2 10.4 4 5 7 5.2 0.6
2 10.4 3 5 8 5.2 1
2 4 2 2 2 2 0
1 1 1 1 1 1 0
0 0 0 0 0 0
0 4 4 5 4.2 0.2
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0 0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
ing three time estimates (or PERT) 88.5

No. of Team members: 4

Daily working hours: 7
No. of Sprint Days: 5
Available hours of work (resources): 140
Accetable Standard Deviation: 15.00%

Deviation (Sd) >Acceptable value - Break down and reestimate

Story ID
Task ID

1
2
0
3
4
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
6
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 Sprint

Stories / Tasks

Choose the area of the domain according to selected User Stories

Define Common Structure and overall design requirements (UI etc)
0
Choose the area of the domain according to selected User Stories
Create a class diagram for the chosen domain
US 1 - For User Story - As a <user>, I want <goal> so that <reason> - Develop / Crea
- Sequence Diagram
- User Interface
- Non Functional Requirements
- Test Cases
- Functionality (Code)
- Tables in Database
- Test it – Approved / Done?
- Implement
US 2 - As a <system>, I want to <run a batch every evening at 9 PM> so I can <print ag
- Sequence Diagram
- Non Functional Requirements
- Design Report Layout
- Test Case
- Functionality (Code) - SQL Report Builder Database
- Test it – Approved / Done?
- Implement
US 3 - For User Story - As a <user>, I want <goal> so that <reason> - Develop / Cre
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Effort "Day 0" calculated using three time estimates (or PERT)

Days in sprint / Effort left

0 1 2 3 4 5 Linear count down based
88.5 70.8 53.1 35.4 17.7 0.0 on the resources available
88.5 74.5 62.5 36.5 36.5 36.5 17.7

8.0 6.0 0.0 0.0 0.0 0.0

24.0 12.0 6.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
8.0 8.0 8.0 0.0 0.0 0.0
12.0 12.0 12.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
3.3 3.3 3.3 3.3 3.3 3.3
2.0 2.0 2.0 2.0 2.0 2.0
2.5 2.5 2.5 2.5 2.5 2.5
2.9 2.9 2.9 2.9 2.9 2.9
10.4 10.4 10.4 10.4 10.4 10.4
10.4 10.4 10.4 10.4 10.4 10.4
4.0 4.0 4.0 4.0 4.0 4.0
1.0 1.0 1.0 1.0 1.0 1.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0
 100.0

90.0
88.5

80.0
74.5
70.0 70.8

62.5
60.0
Effort left

53.1
50.0

40.0

30.0

20.0

10.0

0.0
1 2 3

Days in Sprint
 62.5

53.1
P
D

36.5
35.4 36.5 36.5

17.7

0.0
3 4 5 6

Days in Sprint
PLANNED
DONE
Example: Estimation a Sprint Story Point vs. Person hours

Current velocity is: 22 6.36

The value set on experiences from earlier sprint/projects

Insert for the Sprint

Estimated Story Point 18 Actual result:
==> Actual Delivered Story Point 11
Baseret på antal US/Sprint der er færdige 1 Point eq. to Personhours. The team h
but are actually using this amount of h
Team-members 4 Point
Daily working hours 7 Estimated Hours / SP
Lenght Sprint in days 5 7.8
Available hours in Sprint 140 =C13/C7

From Planning Sheet:

Effort "Day 0" calculated using three point estimates (hours)
Hours recalculated to Story Point based on current velocity (E3)

Dynamic - Measure daily

Day 0 Day 1 Day 2
Planned Hours 88.5 70.8 53.1
Actualt effort left 88.5 74.5 62.5
Diff 0 -3.7 -9.4

Akkummeleret Actual SP done 0.00 0.21 0.73

beregnet pba estimerede SP for sprint (C7) 0.00 0.21 0.52
 Eq. Hours/Story point (=C13/C3)

rsonhours. The team has estimated,

using this amount of hours for each

Actual Hours / SP used

12.7
=C13/C8

88.5
13.9

Day 3 Day 4 Day 5

35.4 17.7 0
36.5 36.5 36.5
-1.10000000000001 -18.8 -36.5

0.79 1.83 3.86

0.06 1.04 2.03
Velocity is a
measure of the
amount of work a
Team can tackle
during a single
Sprint and is the key
metric in Scrum.
Velocity is calculated
at the end of the
Sprint by totaling
the Points for all
fully completed User
Stories.