Re: Estimate Confusion :o)
- Seen some nice answers but why would one use relative weights
calculating complexity, workload... of a story and then go to real
hours? Hours will differ from one team member to another based on
knowledge, experience... and are thus by default wrong if they are
used before knowing who will do the task. Afterward you can not use
them to compare between 2 stories anyway, unless same person has
completed both stories him/herself.
What we did during our process improvements is using the story points
for our task estimations as well, so we keep it relative weights all
the way. Watch out, this will only work if you have a descent
decomposition of your stories & tasks.
--- In firstname.lastname@example.org, "tinachenau" <tinachenau@...>
> Hi Everyone:
> I think I am confused about Product Backlog estimates and Sprint
> Backlog estimates.
> I ask my team member to estimate Product Backlogusing using Story
> Points and then do Sprint Backlog using hours at Sprint Planning
> I have a list of tasks and the ititial time estimates now, say,
> The Backlog Item AAA has 5 story points, Backlog Item BBB has 10
> story points.
> AAA is broke into 3 tasks, task AAA1 needs 4 hours to complete, task
> AAA2 needs 3 hours to complete, task AAA3 needs 2 hours to complete.
> BBB is broke into 3 tasks, task BBB1 needs 4 hours to complete, task
> BBB2 needs 3 hours to complete, task BBB3 needs 2 hours to complete.
> My question are:
> Q1 :what conclusion can you draw from the example above?
> Can I tell that Product Backlog estimates is not good enough?
> Q2: Is there any relationship between story points and hours?
> Q3: Is it right that I can estimate Product Backlog using Story
> points and estimate Sprint Backlog using hours (1 story point <> 1
> hour in my case)