Search the web
Sign In
New User? Sign Up
scrumdevelopment · Scrum Users
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Want your group to be featured on the Yahoo! Groups website? Add a group photo to Flickr.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
sizing the backlog   Topic List   < Prev Topic  |  Next Topic >
Reply | Forward  |  Next Message > 
Re: [scrumdevelopment] sizing the backlog

Hi,

I've been advocating the use of this technique for some years now. We used
it first two a couple of years back. It's quite simple, very powerful
because it emphasizes the relative estimation much more than basic planning
poker.

Here's how I've facilitated it to several teams:


A) Before you start using the technique, you first create a the buckets
with examples (a scale).

For example just start with two items and ask which one of them is bigger,
then add a third item and ask whether that is the same size, smaller, bigger
or in between of those two items in size. We've used buckets in sizes of the
Fibonacci sequence (just like planning poker cards). BTW when you do this
exercise it is better if you have the items written on index cards and
create the initial scale on a table - this way the items are easy to move
and the scale is easy to create.

When you have the buckets ready (usually 2-3 examples per bucket). It's
time to create the physical buckets. I usually have printed out papers with
a box within them which we can use in the backlog estimation meetings (part
B). I have attached the template that I use to create the buckets.

B) When estimating backlog items, bring the scale with you. Also print or
write the items to be estimated on index cards. I really prefer to do this
physically, because a very nice characteristic of index cards is that they
are easy to move, sort and read.

Then, one by one, assign each new item to a bucket based on the items and
examples that already have been assigned into the same bucket. It's very
easy and fast to do the comparison. ('Yea, I think it's about the same size
as these...' or 'It's somewhat bigger then these, so let's put in the next
bucket')

Assigning to the buckets can be done quickly by just comparing and
discussing OR you can do it with planning poker to facilitate also
discussion about the size. Use the latter especially with new teams.

After the estimation session (or couple of times during the session if it
is a long one - say half-a-day or more) go through each of the buckets and
see whether the items really are of the same size. If not, move the items
that you think are bigger or smaller to the corresponding other bucket.


Anyway the advantages of this in my opinion are:
- it facilitates relative estimation better than planning poker (where you
have to 'remember' what estimates you have been given)
- it prevents the estimation inflation or deflation (because the examples
don't move from bucket to bucket - with planning poker estimates sometimes
inflate or deflate with time, because they are based more on your personal
feel of the numbers and their sizes)
- it's very fast

Disadvantages:
- items are sometimes not discussed as thoroughly. Especially if you do not
use planning poker with the bucket estimation, might not discuss the
differences in opinions about the item.

Cheers,
Jukka



Tue Jun 24, 2008 9:22 pm

jukkalindstrom
Offline Offline
Send Email Send Email

Attachment
Story Point Scale.ppt
Type:
application/vnd.ms-powerpoint

On Jun 23, 2008, at 8:58 PM, D wrote:

We have a product backlog with ~70 prioritized items. We have done
planning poker and been able to get through 8 - 10 an hour. I
attended a class taught by Tobias a few weeks back and he talked
quickly about bucketing user stories (using planning poker #'s) instead of
planning poker one by one to get through a large amount when first
starting out with scrum. 
Anybody used this bucketing technique? 
Have any tips in facilitating it?

Derek Mahlitz




Forward
 |  Next Message > 
Expand Messages Author Sort by Date

We have a product backlog with ~70 prioritized items. We have done planning poker and been able to get through 8 - 10 an hour. I attended a class taught by...
D
derekm_maps
Offline Send Email
Jun 23, 2008
5:58 pm

... instead of ... Scrum Trainer, Lowell Lindstrom talked about something similar at the last trainers gathering in March. He called it "Affinity Estimating." ...
Kane Mar
kane_sfo
Offline Send Email
Jun 23, 2008
6:55 pm

Derek, It was in fact Kane Mar's blog post of Lowell's exercise that I was referring to.  So you got to the source immediately.  This list is cool :-) Tobias...
Toby Mayer
tobias.mayer
Offline Send Email
Jun 24, 2008
1:24 am

Hi Derek, ... instead of ... I've used the method in team trainings and I recommend it for handling large number of stories. The way I usually go with my team...
Petri Heiramo
petriheiramo
Offline Send Email
Jun 24, 2008
1:15 pm

... instead of ... Thanks to all who replied(Jukka too), awesome information!!!!...
D
derekm_maps
Offline Send Email
Jun 24, 2008
3:22 pm

Hi, I've been advocating the use of this technique for some years now. We used it first two a couple of years back. It's quite simple, very powerful because it...
Jukka Lindström
jukkalindstrom
Offline Send Email
Jun 24, 2008
9:23 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help