How are each Work items estimated and do these estimates relate to each other?

Written by Reedy Feggins, IBM

RTC 3.0 uses three different attributes to help teams determine which work items should be done during the sprint / iteration. These attributes are: Priority, Ranking and Complexity which are covered in detail in the article Customizing the Agile Planning tools in Rational Team Concert 2.0 provides a thorough discussion of the topic with screenshots from RTC 2.x but still remains valid in the RTC 3.x release.

Can you provide some guidance on the relative ranking when assigning this to stories?

The Level of effort estimate is captured using the complexity attribute for Stories where the Story Points are often used.  In some implementations Epics don’t have a complexity attribute while level of effort estimate for a Task is almost always captured in Hours, see figure below.

By default RTC complexity ranking for the Story work item uses Story Points.  In Agile, a Story Point is a unit less measure of time that teams use to estimate to estimate the work that the team will commit to in a sprint. Story points are NOT meant to be directly mapped to calendar time (days/hours) for estimation but instead are mean to help teams create better estimates, often using relative estimating techniques called Poker planning.

RTC Epic - Story - Task Estimates

What is the default to be used for the complexity ranking?  We have 1,2,3,5,8,13, 20, and 40,100.  Is it recommended to modify this?

Estimates using story points mean that if you estimate two stories; one story was estimated as a one and the other story as a value of five, then the second story is 5 times bigger than the first. If a third story is estimated as a ten then it is 10 times bigger than the value of one. Why? so that when you know your team’s velocity equals 10 and you select a 1,2,3 and 5 point story for a sprint, you know they actually add up to a sum velocity of 10.

Studies have found that most people can estimate smaller numbers better but as the number become larger people estimates become less and less accurate so the larger the estimate, the larger the error.

We should give the scrum master some guidance on this relative ranking.

While some teams use a doubling sequence (1,2,4,8…), most Agile teams start off with Story estimates based on the Fibonacci sequence (1,2,3,5,8,13…), which is the default RTC complexity attribute. This mathematical sequence is used for relative ranking. In this approach when estimating, teams are not allowed to pick a number that doesn’t exist in the sequence.[1]

§         http://blog.mountaingoatsoftware.com/tag/story-p

§         http://agile-commentary.blogspot.com/2009/02/create-proper-estimate-scale.html

§         http://loicbar.me/2010/10/24/why-should-you-use-story-points-instead-of-hours/

§         http://agilesoftwaredevelopment.com/blog/jackmilunsky/significance-story-points


[1] APA: Agile Commentary: Create a Proper Estimate Scale… (n.d.). Retrieved 02-20-2011 from http://agile-commentary.blogspot.com/2009/02/create-proper-estimate-scale.html

Advertisements
About

About the Author Reedy Feggins, Jr, is a Solution Architect and Agile Coach at IBM Software, a global software development company. Reedy is a certified ScrumMaster and PMP certified Project Manger. In this role, he trains, mentors and coaches teams in implementing practices such as Scrum, XP and Disciplined Agile Delivery (DAD). Reedy is also a IBM subject matter expert (SME) supporting the adoption of several IBM software development tools: Rational Team Concert (RTC), Rational Quality Manager (RQM), Rational Requirement Composer (RRC), RequisitePro, ClearQuest and ClearCase. He has extensive experience mentoring teams over the past four years has given him the ability to assess business needs, craft an adoption strategy and provide organizations with practical experience implementing the appropriate Agile adoption strategies. My Linkedin Profille http://www.linkedin.com/profile/view?id=9488217&authType=name&authToken=yYEC&pvs=pp&trk=ppro_viewmore

Tagged with: , , ,
Posted in Agile, Planning, RTC, Scrum

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 88 other followers

Blogs I Follow
Agile and ALM

Swimming against the waterfall...

DevOpsGuys

Web Management. Simplified.

BJ Dooley's IT Toons

Cartoons by BJ Dooley for the IT industry.

Disciplined Agile Delivery

An agile process decision framework for the enterprise

Dan Toczala's Blog

THINK - About what's possible....

Best Practices for Building Software Platforms

Best practices, methodologies, technical observations, and other stuff for building better software. Authored by Jim Ruehlin.

Crossbolt

Technology and Project Management: through the eyes of a hired gun

The WordPress.com Blog

The latest news on WordPress.com and the WordPress community.

%d bloggers like this: