Loading ...
Sorry, an error occurred while loading the content.

Re: How do you track actual time spent on tasks

Expand Messages
  • tony_t_tubbs
    ... converting ... hours. ... Right. The message I got was that conversion between units doesn t help, and tracking actuals doesn t either. Just decide on
    Message 1 of 17 , Jan 24, 2009
      --- In scrumdevelopment@yahoogroups.com, Adam Sroka <adam.sroka@...>
      > On Fri, Jan 23, 2009 at 6:50 PM, Adam Sroka <adam.sroka@...> wrote:
      > > On Fri, Jan 23, 2009 at 12:16 PM, tony_t_tubbs <tony_t_tubbs@...>
      > >> --- In scrumdevelopment@yahoogroups.com, Ron Jeffries
      > >> <ronjeffries@> wrote:
      > >>>
      > >>> Hello, tony_t_tubbs. On Friday, January 23, 2009, at 10:02:55 AM,
      > >>> you wrote:
      > >>>
      > >>> > So, as a sanity check maybe, blah blah blah...
      > >>>
      > >>> Yes. In my opinion, this is pointless. The thing is to look at the
      > >>> backlog, figure out how much you can do, look each other in the
      > >>> eyes, and commit to it.
      > >>
      > >> Something else occurred to me this morning about why we are
      > >> to hours, and that is that our burndown spreadsheet tool tracks
      > >> Still, the message that the way we are currently going is pointless
      > >> is coming through loud and clear.
      > >>
      > >> I am going to forward a link to this thread to the team and see where
      > >> that goes. We've had discussions around many, if not all, of the
      > >> other issues you've pointed out as problem areas. Maybe we can take a
      > >> few lessons from here and take another step.
      > >>
      > >
      > > I don't think that what you are doing is pointless. Estimating in
      > > ideal hours has it's proponents including, notably, Kent Beck (the
      > > author of Extreme Programming). They are in the minority in the Agile
      > > community, but they do exist and they have their points (hehe.) I
      > > think that it is worthwhile for you to investigate and come to your
      > > own conclusions as a team. Again, take a look at Mike Cohn's book,
      > > which is the most thorough treatment currently available.
      > >
      > P.S. I think what Ron was saying was that attempting to convert story
      > points to hours is pointless, and I agree. What I am saying is that
      > you shouldn't take that to mean that tracking hours is pointless.
      > Tracking hours has its advantages and disadvantages and you will need
      > to find out what works for you. If you want to track hours you might
      > consider estimating in ideal hours as well. *Read /Agile Estimating
      > and Planning/'*

      Right. The message I got was that conversion between units doesn't
      help, and tracking actuals doesn't either. Just decide on our unit of
      choice and stick with it for a while. Adjust if/as we need to.
    Your message has been successfully submitted and would be delivered to recipients shortly.