LOGIN | REGISTER NOW | SUBSCRIBE
 
Print

Escaping from the “How Long?” time trap


By Joel Semeniuk
Email
March 28, 2011 —  (Page 1 of 3)
If it is true that time is money and, once lost, can never be found again, it should be no surprise that the “work smarter, not harder” mantra has become the drumbeat that agile developers must march to. One pillar of project estimation is having a solid grasp of how long will a given task take, and how long to complete the entire project.

Even for those who have a strong grasp of this concept, delivering truly accurate estimates can become a frustrating, time-consuming process that results in projections that are far off the mark. Why? Because falling prey to the wiles of the “time trap” is easy, even for the most seasoned professionals.

Conventional wisdom dictates that tracking time against estimated tasks enables more precise comparisons between actual and planned estimates. In theory, this should allow for greater accuracy and better estimation practices.

However, the truth is that more often than not, time tracking becomes a trap—a perilous sinkhole masked by a seductive façade—that sucks in developers, project managers, and whole teams. One of the greatest dangers posed by the time trap is inaccurate estimates that result in hazardous outcomes, including overruns and a drop in the perceived value of the project (and by extension, individual developers and the team at large).

Some people can become bogged down in the minutiae of accounting for every minute spent on tasks or projects. The relentless drive to capture more and more data can become a serious obstacle, a bottleneck leeching away productivity that prevents project stakeholders from completing critical work at hand. Too often, it seems that time tracking can devolve into an intrusive burden, imparting the feeling that Big Brother is peering over people’s shoulders.

With so many diverse tasks needing attention throughout the workday, accurately tracking and recording time spent on each individual item is inherently troublesome. So, while most developers try to honestly account for their day, trying to make the numbers add up to a full eight-hour day can result in unintentionally fuzzy time-keeping, ensuring that future estimates based on this data are inherently inaccurate.


Related Search Term(s): agile, time-tracking

Pages 1 2 3 


Share this link: http://sdt.bz/35401
 
Most Read Latest News Blog Resources
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
LEADTOOLS HTML5 add-on modules released
Including New HTML5 Zero Footprint Viewer, JavaScript Libraries and RESTful Web Services for Document and Medical SDKs
How to speed up your Cukes
Using a five-step process derived from Six Sigma, Cucumber tests can go much faster
WhiteSource offers open-source license management as a service
Software gives companies insight into the open-source components in products
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter



Comments


03/29/2011 06:00:07 AM EST

I tend to agree. As a developer myself I do find it very hard to remember what I did on a particular day, particularly by the end of the week. I hated it so much I actually invented a tool to do it for me (Qlockwork). With my management hat on, however, I can see why there is a need. If you can use an Agile approach it becomes much less of an issue and I believe you can use developers more efficiently. However, many businesses prefer a more waterfall approach where you know (or try to) exactly what you'll deliver and when, which does require very good estimation, and for that you do need feedback on estimate accuracy. Anne Currie http://www.qlockwork.com

United KingdomAnne Currie


Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Finding the right tool for the agile job
Experts emphasize that tools should bolster the agile process above all else Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
MAY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
05/16/2012 12:45 PM EST

How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
05/14/2012 12:18 PM EST

Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
05/12/2012 07:05 PM EST

The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
05/10/2012 06:39 AM EST

The Rise of the Brogrammer, or the Rise of the Sexist Programmer?
Women in Silicon Valley get vocal about sexist ads and campaigns that contribute to a tense work environment.
05/09/2012 03:14 PM EST

Retriever Communications Releases RADE3
Organizations concerned about the growing popularity of bring your own device to work policies may be comforted by the release of RADE3.
05/09/2012 11:46 AM EST

 

Events calendar tab
Lean Software & Systems
5/13/2012 to 5/18/2012
Boston
Lean-Kanban University

IDUG DB2 Conf.
5/14/2012 to 5/18/2012
Denver
IDUG

Business Analytics Innovation Summit
5/23/2012 to 5/24/2012
Chicago
IEG

IBM Innovate Conf.
6/3/2012 to 6/7/2012
Orlando
IBM Rational

Agile Development Conference West
6/10/2012 to 6/15/2012
Las Vegas
SQE