0% found this document useful (0 votes)
8 views8 pages

Project Management Tips

Download as pdf or txt
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 8

Agile Team Definition and Capacity Analysis

Agile Team
Product Owner
Scrum Master

Application / Module / Specialization

Purpose of Team / Defining Characteristics


Instructions for Time and Resource Calculations

Sprint Start Date Complete table at left. Include all activities that involve all team
Sprint End Date members. Subtract activity hours from Work hours in Sprint to get
Workdays in Sprint 10 Net work hours in Sprint. Then fill out the Team table using the
Work Hours in Sprint 80 formulas below.
Skills Daily Scrum hours 2 <= 0.25hrs * 8 days
Sprint Prep hours
Sprint Planning hours 4 <= 2hrs for each week in Sprint
Task Breakdown hours
Team Review hours 2 <= 1hrs for each week in Sprint
Retrospective hours 1 <= 0.75hrs for each week in Sprint
Net Work Hours in Sprint 71 Hours = Net work hours in Sprint - Hours off

Team Member Role / Skill Set % Avail Hrs Off Hours Hours: Hours available to work on the Sprint
100% 71.00

Team Hours = Sum of Hours for all team members


ie Total working hours available for a Team in a Sprint

Net Team Resources = Team Hours / (Work hours in Sprint)


ie Effective # of of full time resources

Points Available = Team Hours / 8 {eq. of Days}


Net Team Team ie Total work a Team can do in a Sprint (days)
Points Available: 8.9 0.8875 71.00
Resources: Hours:
Estimation

 Estimation is done for the following reasons:


–Provide transparency to the actual cost of work.
–Provide predictability to the organizations work capacity.

 What do we estimate?
–Stories
–Tasks

8
A Closer Look: Task Estimation

Task Breakdown, Task Level Estimation


The technique selected for Task Level Estimation is ‘Absolute’ hours

 Estimation is done at the Task level with “Absolute Hours” using the
Fibonacci scale. The values are hours per person.

0, 1, 2, 3, 5, 8, 13, 21

10
What is a Spike?

 There are situations in which the team simply don't know enough about a
Story to be able to provide an estimate. In that case, the activity known as
a Spike would be performed.

 The definition of a spike is a timeboxed research period to allow the team


members to gain insight into what is required to implement a story. The
outcome of the spike, is that the team can then provide an estimate for
the story.

Note: a spike should be limited to one to five days.

11
Plann l Actual
Actual ed Actual a Actual Planned QA Planned Actual Planned Total
Dev Dev Dev n QA QA Veloci QA QA QA QA Actual Planned Total
Iteration Iteration Resou Resou Velocity n Resou Resourc ty/per Points/t Points Points/t Point Story Story Story
Release [#] Date rce rce /person e rce e son eam /team eam s points points Points
1106 4/13/11 3 6 45 2 4 4 5 8 20 385 20 50 960
1.00
1107 4/27/11 4 6 45 2 4 4 5 16 40 385 44 100 960
1108 5/11/11 4 6 45 4 4 4 5 32 60 385 76 150 960
2.00
1109 5/25/11 6 6 45 4 4 4 5 48 80 385 116 200 960
1110 6/8/11 6 6 45 4 4 4 5 64 100 385 156 250 960
3.00
1111 6/22/11 3 6 45 5 4 4 5 84 120 385 188 300 960
1112 7/6/11 8 6 45 5 4 4 5 104 140 385 240 350 960
4.00
1113 7/20/11 8 6 45 5 4 4 5 124 160 385 292 400 960
1114 8/3/11 8 6 45 5 4 4 5 144 180 385 344 450 960
5.00
1115 8/17/11 8 6 45 6 4 4 5 168 200 385 400 500 960
1116 8/31/11 8 6 45 6 4 4 5 192 220 385 456 550 960
6.00
1117 9/14/11 8 6 55 6 4 4 5 216 240 385 520 600 960
1118 9/28/11 8 6 55 6 4 4 5 240 260 385 584 650 960
7.00
1119 10/12/11 8 6 55 6 4 5 5 270 280 385 654 700 960
1120 10/26/11 8 6 55 5 4 4 5 290 300 385 714 750 960
8.00
1121 11/9/11 8 6 55 5 4 4 5 310 320 385 774 800 960
1122 11/23/11 8 6 4.5 5 5 4 5 5 335 340 385 835 850 960
7.00
1123 12/7/11 7 6 4.5 5 5 4 4 5 355 360 385 886.5 900 960
1124 12/21/11 7 6 4.5 5 5 4 5 5 380 380 385 943 950 960
8.00
1125 1/4/12 7 6 4.5 5 5 4 4 5 400 400 385 994.5 1000 960

Burnup Chart Data from Excel


Dev & QA Actual/Planned
700

Actual Dev Points Planned Dev Points Total Dev Points Total QA points Actual QA Points Planned QA Points

600
Dev Points

500

400 QA Points

300

200

100

0
4/13/11 4/27/11 5/11/11 5/25/11 6/8/11 6/22/11 7/6/11 7/20/11 8/3/11 8/17/11 8/31/11 9/14/11 9/28/11 10/12/11 10/26/11 11/9/11 11/23/11 12/7/11 12/21/11 1/4/12
1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125
1.00 2.00 3.00 4.00 5.00 6.00 7.00 8.00 7.00 8.00

Burnup Chart on Excel


Note:
JIRA Burnup chart

You might also like