Time tracking is a common curse word in the office. Once mentioned it often creates panic and confusion not only between the employees but between the managers as well. However, despite its bad reputation, the concept has proven time and time again to bring great benefits beneath those of simply keeping time. This week we decided to share a story about one of our clients that benefitted greatly from simply starting to track time.
The client is a Lithuanian accounting firm that offers business consultancy and other services on the side. The company has been growing and expanding for years, all the while, little attention has been paid to not only growing the business but also to implementing the right processes. It all changed a little over a year ago, when the management decided to fix the messy processes in order to bring efficiency and clarity into the day to day operations. That is when they found us.
Time tracking is a valuable concept for many projects. It allows managers and team members to organize their work more efficiently, plan ahead, complete projects on time and within budget. However, in reality most of the time tracking attempts fail within the first few months of being implemented and while the teams and projects where time tracking is implemented are quite different, the reasons why time tracking does not work are more or less the same.
Time tracking has evolved a great deal from the initial time sheets that were used to calculate the payroll of the employees. While it is still being used in that manner, a lot of additional uses such as project time estimation, project cost and employee productivity have been found. However, despite all the benefits that time tracking may bring to the team, there are still problems that managers are facing when trying to implement it and the first one they usually come upon is the human factor.
Nowadays you will find less and less people who still haven’t heard anything about Agile framework called Scrum. Those, who already learned about it one of the first things they met was the concept of a “Story point”. Story point is a measure of size of a user story, feature or other piece of work but not equal unit of time. Story points are used by Scrum teams and provides with forecasts on total effort needed to deliver task.