Re: using story points to estimate tasks
- I know this has been heavily discussed but I wanted to throw my 2
cents in as well. On our team, we are still learning the basis of
formulating story points for our *stories* heh, estimating our tasks
is basically boiled down to making sure each task is held under a
I see the importance of being able to develop proper story points to
gauge an idea of a long term plan but for tasks, at least in our
case, we like to have hour estimates because it keeps everyone in
the proper mindset that they want to see the blue bars go down and
the green bars go up.
Just having our burn-down, burn-up charts in our team room provided
the team with a way of , keeping focused on our new process and not
let any old habits or mentality slip back in.
While still new, I think we are learning slowly.
--- In email@example.com, "Tobias Mayer"
> I recently heard that some CSM trainers are recommending that
> story points to estimate the size of tasks. This baffles me. Ithink
> they are called story points for a reason: they are used tomeasure the
> relative size of stories.ensure
> I don't encourage teams to estimate task size at all except to
> that a task is small enough to move from "In Progress" to "Done"in a
> single day, but I understand that some teams successfully use realtime
> (i.e. hours) to estimate task size. I think it is an unnecessary,Should
> perhaps even wasteful practice, but at least it makes sense.
> I can't make sense of the idea of sizing tasks in story points.
> all the task-story-points add up to the total size of the story?What
> if you add a new task later on? I'd be very interested inhearing how
> this system works, how it helps. My instinct is to dismiss it...but I
> have made that mistake before (!) so now I seek enlightenment.Anyone?
> http://agilethinking.net <http://agilethinking.net>