1. Home
  2. Reporting
  3. Time Tracking (Timesheets)

Time Tracking (Timesheets)

Overview

Largely a relic from “the way we’ve always done it…”

What is the purpose of developers logging time sheets – for your organization?

Are you a cost center billing back to business units?  Are you trying to estimate how long things will take or how much effort is remaining?

Time Tracking is Anti-Scrum: What do you do when you need it for billing?  (by  – co-creator of Scrum):

“…at IBM and elsewhere that asking developers to fill out time sheets reduces team productivity by at least 10%. They hate to do it, it is duplicate work, it is obviously “waste”, and is only done by companies that do not have a clue about lean product development.”

Time Tracking is Anti-Scrum: What do you do when you need it for billing?

 

5 Reasons to Kill Timesheets (by Joanne Perold, Agile42)

Time sheets erode trust, treat people as “resources” vs humans, promote individuals over team mentality, don’t directly satisfy a management reporting need accurately and are a poor measure of productivity.

https://www.agile42.com/en/blog/2014/08/21/5-reasons-kill-time-sheets

 

Some Stack Overflow Discussion…

https://stackoverflow.com/questions/1607214/time-tracking-in-scrum

Updated on October 19, 2017

Was this article helpful?

Related Articles