Should Developers Time Track?

I have yet to meet a developer who enjoys time tracking. It has the smell of micromanagement, and seemingly adds overhead to our daily routine for reasons we don’t understand. From an organizational perspective, time tracking provides a treasure trove of data. Being able to understand where employees are spending their time can assist in making strategic decisions, identifying problems, and assist with billing clients. The truth is this same data can also serve as a treasure trove to the developer. Being able to understand where you spend your time helps you to better structure your day, eliminate waste, and identify bad habits over time. For example, perhaps you are spending too much time responding to emails and not getting any other meaningful work done. So why are developers so resistant to tracking their time? Below are a couple of reasons I’ve heard from some of the developers I’ve managed: <h2>The feeling that big brother is watching me</h2> Needing to account for your time on the surface feels like a lack of trust an employer has for an employee. Employers shouldn’t focus on a specific individual’s time data unless there is a concern that an individual is underperforming or not putting in the appropriate time. Possible Solution: What if the submitted time data was anonymous and the employer can only see the time spent but not by whom? That would still provide a mountain of data to the organization while allowing developers to feel protected. <a href="https://medium.com/@comp87/should-developers-time-track-62dd3277eaa5">Click Here</a>