3 ms·
Sounds about right. At my employer, DevOps expects that we fill in our time sheets completely in order to represent the whole eight hour workday. So we do. Thin
by BitwiseFool 5y ago
Sounds about right. At my employer, DevOps expects that we fill in our time sheets completely in order to represent the whole eight hour workday. So we do. Things like taking breaks, talking to coworkers, waiting around for answers from other teams, meetings, etc., all of that goes towards active project work. However, the projects are estimated using effort hours and they do not include inflated 'we need to look productive the whole day' tasks.
If an individual goes under the full eight hours, it reflects poorly on them during evaluations. If the division goes overtime on project hours, nothing bad happens. So naturally each developer is incentivized to jot down extra time and disincentivized from tracking time truthfully. And yet management wonders why we go overtime on so many buckets!
And everyone knows the numbers aren't real, yet the song and dance must go on. I really wish we had a term for this in English. I suppose 'Potemkin' sort of applies?