title: Time Tracking and Agile Methodology
body: <p>I work in a large outsourcing company based in India. I am in the US and have a team of 3 developers and we are using scrum practices and have had great success with our approach.</p>
  
  <p>My problem is that our company requires us to estimate time on activities monthly whereas we work on weekly iterations. The system provides a list of 45 activities. To give an example of how granular it gets, we have activities like Coding, Coding Review, Coding Rework.</p>
  
  <p>Now everyday we are supposed to enter actual time aginst these activies. And to make things worse the system for time tracking is very poorly designed and is very slow.</p>
  
  <p>The rationale the management has behind this process is that they want to use this time logged to forcast future work. But the problem is that there are no processes in place to ensure that we enter correct time. So we end up putting any numbers and the end of the day.</p>
  
  <p>This is affecting productivity and morale of the team and defeating the whole purpose.</p>
  
  <p>What are you thoughts on Time tracking in an Agile projects? </p>