GEEK SNACK
ThoughtWorks
Agile linear algebra question paper
Test your liner algebra
Releasing planning, Iteration planning, velocity and
burn up charts are basic linear algebra!
From Wikipedia: “Algebra is a part of mathematics
(math) that helps show the general links between numbers
and math operations (adding, subtracting, multiplying or
dividing) used on the numbers. Algebra does this by using
letters (a,b,c,...) or other symbols to represent numbers,
either because the numbers are unknown or because the
numbers change during the course of the problem, in
which case the letters are called variables.
Let’s test your basic Agile linear algebra knowledge!
Check out the formulas below and try out the
questionnaire. You can find the answers at
http://www.agilegeeksnack.com
The Formulas
Vp = Ro / i
The planned average velocity (Vp) is the number of story points
planned for the release (Ro) by the number of iterations (i).
V = ∑Si / i
The average velocity of a team (V) is the number of delivered
story points per iteration (∑Si) by the number of iterations (i).
Ve = V + ∆V
Velocity expected is the average velocity (V ) plus the expected
velocity variation (∆V). Velocity expected is commonly used for
planning activities, such as iteration and release planning.
R = Ro + ∆R
The current total story points planned for the release (R) is the
original story points planned for the release (Ro) plus the delta
of story points for the release (∆R).
Rm = R - ∑Si
The number of story points remaining for the release (Rm ) is
the current total Story points for the release (R ) minus the sum
of completed story points for the iterations (∑Si).
Ir = Rm / Ve
The number of iterations remaining (Ir) is the number of story
points remaining for the release (Rm ) by the expected velocity
(Ve)
Paulo Caroli
May 01, 2009
Episode 1
Questionnaire
Exercise 1
An agile team plans to deliver 400 story points in
10 iterations. What is the planned average velocity
for the team?
(a) 10 sp/it (b) 20 sp/it (c) 30 sp/it (d)40 sp/it (e) other
Exercise 2
A team has average velocity of 10 sp/it. Extra
resources are added to the team, thus creating an
expected raise in velocity of 4 sp/it. What is the
expected velocity for the team?
(a) 10 sp/it (b)14 sp/it (c)4 sp/it (d)6 sp/it (e) other
Exercise 3
In Iteration 1, the team delivered 10 story points,
in iteration 2 the team delivered 14 story points, in
Iteration 3 the team delivered 12 story points.
What is the average velocity for the team?
(a) 6 sp/it (b) 12 sp/it (c)24 sp/it (d)36 sp/it (e) other
Exercise 4
Consider the team iteration history of Exercise 3.
The original release plan is to deliver 400 story
points. Assume that the team (which did not
change from iteration 1 to iteration 3) is able to
keep the same average velocity from the first 3
iteration for the remaining iterations of the
release. The project manager decides to add an
extra dev pair to the team; and the velocity is
expected to increase by 2 sp/it. How many
iterations will it take for the team to deliver the
400 story points planned for the release?
(a) 12it (b) 16 it (c)26 it (d)36 it (e) other
Exercise 5
Same as Exercise 4, but 140 sp have been de-
escoped from the release. How many iterations will
it take for the team to deliver the number of story
points planned for the release?
(a) 12it (b)16 it (c)26 it (d)36 it (e) other
Exercise 6
Same as Exercise 4. How many story points should
be de-scoped from the release to enable the
software to be released after 12 iterations?
a) 0sp (b)112 sp it (c)196sp it (d)238 it (e) other