> changes can take literally 20 times as long as they should while we work out what the existing code does
I imagine you have to sell the extra time to (aka convince folks this is the right path) _somebody_. Maybe I've been working at the wrong places :) .
> Maybe I've been working at the wrong places :).
I think it's a balance between keeping certain key tasks beyond the radar of PM's (so you have time to think and act) and doing enough "deliverables" to keep them happy.Sadly, PM's in many places have ground-down that buffer to the point where you're maxed out on your backlog and they know everything that's in it. Or worse, they're creating fake deadlines to fabricate "urgency" so that you're no longer in control of the minutes in your day.
i've definitely had PMs do this to me when projects were wrapping up and they didn't have any real work to give me. I'd just work at the regular rate and no surprise- no one squawked when i blew past the deadline for the busy work. It's mismanagement imo, with enough experience you start to resent being treated like a precocious child with adhd
The only part of the process that's optional and could theoretically be skipped is turning your notes into documentation consumable by others, but that's a pretty small portion of the time spent.
My real question is, how did the business/management learn that they had "a choice between doing it in 20X time and not doing it at all"? How did those lessons get learned?
This happens less now that we assume any existing piece that we don't know about already will turn out to be a minefield.
How does "the business" feel about this situation?
How does the team feel about it?