My experience with time trackers is a bit more positive as we use one for project management purposes only. So we just log our time against our weekly tasks and use these stats for more accurate planning.
Though, at one of the places I worked, they used DeskTime that recorded our comp activity, inactivity time, app time, website visits - literally everything. I still feel dread and horror remembering that I had to check my stats and make sure that I was doing fine even though I'd never slacked off. I couldn't stand the pressure and quit in a few months. But simple time trackers work just fine by me.
At my last job we did estimated hours on tasks. I guess I wasn't really thinking of that as time tracking. Sometimes we would get scolded if we forgot to put hours in. But the main issue I had with it was that I often found that the tasks (or hours) I planned didn't work out to be what I actually needed to do once I got into it. And it can be a bit tedious to keep all that synced with reality.
When I formed this team, we started out doing the same thing but after a while we decided to try dropping the hours for a sprint as an experiment. And we never went back to it. Because playing a shell game with the hours provided no real benefit. Later we dropped preplanning of tasks too for the same reason. We work at the story level. It is still quite valuable to do some initial design work for each story, but that doesn't always translate easily into discrete tasks. So it isn't a requirement to task everything out ahead of time. Devs can choose to use tasks to help them keep track of things if they want.
Thank you for sharing, Kasey!
My experience with time trackers is a bit more positive as we use one for project management purposes only. So we just log our time against our weekly tasks and use these stats for more accurate planning.
Though, at one of the places I worked, they used DeskTime that recorded our comp activity, inactivity time, app time, website visits - literally everything. I still feel dread and horror remembering that I had to check my stats and make sure that I was doing fine even though I'd never slacked off. I couldn't stand the pressure and quit in a few months. But simple time trackers work just fine by me.
At my last job we did estimated hours on tasks. I guess I wasn't really thinking of that as time tracking. Sometimes we would get scolded if we forgot to put hours in. But the main issue I had with it was that I often found that the tasks (or hours) I planned didn't work out to be what I actually needed to do once I got into it. And it can be a bit tedious to keep all that synced with reality.
When I formed this team, we started out doing the same thing but after a while we decided to try dropping the hours for a sprint as an experiment. And we never went back to it. Because playing a shell game with the hours provided no real benefit. Later we dropped preplanning of tasks too for the same reason. We work at the story level. It is still quite valuable to do some initial design work for each story, but that doesn't always translate easily into discrete tasks. So it isn't a requirement to task everything out ahead of time. Devs can choose to use tasks to help them keep track of things if they want.
Well, estimating is harder than it seems. Most of us tend to either underestimate or overestimate our efforts; accurate estimations are rare.
I'm a bit surprised to learn this approach works for your team, but I'm happy to know that it does!
Thank you again for sharing 🙏