We do track hours remaining. We used to review them and talk about the actual vs estimate amounts. After 2 - 3 years of being here, I still find that eachMessage 1 of 28 , Sep 13, 2010View SourceWe do track hours remaining. We used to review them and talk about the actual vs estimate amounts. After 2 - 3 years of being here, I still find that each individual task is all over the place (-25%, +30%, etc) but that as a whole, we are fairly accurate. We still track time but don't really do anything with it anymore.RickOn Mon, Sep 13, 2010 at 5:34 AM, Wouter Lagerweij <wouter@...> wrote:
Hi,On page 13 of the (current:-) Scrum Guide (http://www.scrum.org/scrumguides/) it says: "Tasks should have decomposed so they can be done in less than one day."I don't know whether that was there in an earlier version of the guide, but I just happened to have read that last week, because I wanted to try out the "scrum open" assessment thing.I have been trying to encourage people to keep tasks small for a while, though. It results in such a nice "we're moving things along" feeling.WouterOn Fri, Sep 10, 2010 at 8:16 PM, Steven Janvrin <sjanvrin@...> wrote:
Hi Wouter - where did you get the 1 day maximum task length? Just curious as to the source.
To: email@example.comFrom: wouter@...
Date: Fri, 10 Sep 2010 11:05:38 +0200
Subject: Re: [scrumdevelopment] Tracking Actual Work Done
Hi,I rather agree with what Lance is saying: your tasks are too big. Default for Scrum is a maximum length of 1 day for a tasks. I try to encourage my teams to aim for less than half a day.If you notice that tasks are In Progress during your stand-up that were already In Progress the day before, that gives an opportunity to ask what is going on there. Same for too many tasks being open concurrently.In teams where we had trouble finishing tasks in such a period, we started marking tasks (simply putting a dot on it with a marker pen) to get an idea of which tasks were having problems. That made things visible enough to become a high priority in the retrospective, and to get the team to try and make smaller tasks in the planning meeting.And with tasks kept small, it's very plain how much time (roughly) is still left by simply looking at the number of tasks left.Wouter
On Thu, Sep 9, 2010 at 4:54 PM, sjanvrinxx <sjanvrin@...> wrote:
Currently our team is only tracking three states for a task - Defined, In Progress and Completed. We do not track actual time worked against each task during the course of the sprint, and task completion goes from zero to 100 percent as a binary update.
I'm starting to believe we should be tracking actuals during the sprint as well, but I don't want to devolve into a command and control situation. What's the consensus of the group on tracking actuals in manner consistent with Scrum philosophy?Thanks,