Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
LLAMS36633yI think its toxic at best. It implies that you should be spending every minute of every day working on tickets. It leaves no room for personal growth or even just feeling a bit burned out one day. Also tracking how much time a ticket takes is a waste of time and another toxic practice IMO.
-
Maybe it helps to get metrics on how much time was spent on each ticket. Of course it won't be accurate, but at least it's something. From dev perspective it's ok as long as the tracking doesn't require more work.
-
I always feel the desire to add 20 minutes "writing down my hours" in to my tracking.
Add that to the 1 hour of reading emails that aren't anything to do with me and the 2-3 hours meetings that could have been a 10 second comment and it's fun to start locating why that job that should have been completed today is still way off. -
It’s never welcomed by devs and yes I have written down “record timesheet - 20 min” on the timesheet, if someone pushes me for that level of details
I think it makes sense if customers want to know how they’re being charged and take that as a reference. Some others have to do it for tax purposes or whatever. Bottom line is, we all gotta accept the timesheet is never accurate or should be very detailed. -
LLAMS36633yI worked in a team once that enforced this. While it is true that it can sometimes be done for billing/tax purposes, in my experience it was done to compare the estimated time of the ticket against the actual time spent on it. Then management could grill devs for going over time. Also for making sure we basically werent spending any time on anything not directly related to sprint tasks.
It was used as a means to monitor us and blame us for work not being finished at the end of the sprint. It had no other benefit.
I work on a team now that does none of this. We dont have to log all our time and we dont have to fill in timesheets. And we are much more productive than that other team can ever hope to be.
Related Rants
Do you think tracking work hours by ticket makes sense?
I think it's a waste of dev time. Not sure from PM pov.
rant
ticket
hours
work
issue