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

57587Re: [SCRUMDEVELOPMENT] Time tracking for building software

Expand Messages
  • Greg Robinson
    Dec 17, 2013
    • 0 Attachment

      Thank you to all that have responded!  Your feedback and articles have been tremendously helpful!


      On Dec 17, 2013 2:38 PM, "Charles Bradley - Professional Scrum Trainer and Coach" <chuck-lists2@...> wrote:


      You might also want to see this article about Scrum time tracking written by Scrum Co-Creator Jeff Sutherland:


      Charles Bradley
      Professional Scrum Trainer
      Scrum Coach-in-Chief

      From: Kurt Häusler <kurt.haeusler@...>
      To: SCRUMDEVELOPMENT@yahoogroups.com
      Sent: Tuesday, December 17, 2013 7:14 AM
      Subject: Re: [SCRUMDEVELOPMENT] Time tracking for building software

      Hi Greg,

      most companies I have worked at that used Scrum required such time tracking. Mostly because the information was required for their time & materials billing approach. Sometimes to give the PMs an idea about how much they need to scale developer estimates (I mean initial hour estimates required to write a customer offer, not the agile estimating used in sprint and release planning) in order to get numbers they can put in a offer or contract.

      I am opposed to it, and see it only leading to many types of dysfunction. It simply doesn’t suit the nature of the work.



      On 16 Dec 2013, at 17:59, Greg Robinson <z00foodagile@...> wrote:

      > Companies that want to capitalize their expenses for building software need their development teams to track time they spend on building and testing software.  Has anyone heard of a company requiring their teams to track the time they spend as part of the tasks in the Agile Project Management Tool being used?
      > For example, if a user story consists of 5 tasks and task1 was estimated at 6hours but it only took 3 hours to complete, than the developer is required to enter the actual effort of 3 hours into the tool for time tracking purposes.
      > I can understand tracking the estimated vs actuals over the course of a sprint or two in order to help improve team agility and estimation practices, but I've never heard of it being mandated as a time entry system.  This can be a problem particularly for mature teams that don't use tasks or task hours.
      > What have you seen work?  What downsides do you see to this?
      > Looking for comments or thoughts.


      To Post a message, send it to:  SCRUMDEVELOPMENT@...
      To Unsubscribe, send a blank message to: SCRUMDEVELOPMENT-unsubscribe@... Groups Links

      <*> To visit your group on the web, go to:

      <*> Your email settings:
          Individual Email | Traditional

      <*> To change settings online go to:

          (Yahoo! ID required)

      <*> To change settings via email:

      <*> To unsubscribe from this group, send an email to:

      <*> Your use of Yahoo Groups is subject to:

    • Show all 18 messages in this topic