We are implementing the feature in this two week sprint. (It is a four week task and is not amenable to being further decomposed - at least not with meaningful exit criteria.)
PM: “How long is developing this feature going to take?”
Me: “Due to all the refactoring that’s needed --which I’ve been repeatedly bringing up for two years – just to implement it, it’s going to take about 6 months.”
PM: “Is there any way you can have it ready for the release in two weeks?”
Me: “No.”
PM: Proceeds to tell everyone that it will be ready for the release in two weeks.
You are missing the parts where they pull the wildest possible estimate out of their ass, then blame the worker for not living up to it.
Oh uh… is that just me? Okay then…
We are implementing the feature in this two week sprint. (It is a four week task and is not amenable to being further decomposed - at least not with meaningful exit criteria.)
PM: “How long is developing this feature going to take?”
Me: “Due to all the refactoring that’s needed --which I’ve been repeatedly bringing up for two years – just to implement it, it’s going to take about 6 months.”
PM: “Is there any way you can have it ready for the release in two weeks?”
Me: “No.”
PM: Proceeds to tell everyone that it will be ready for the release in two weeks.
Never let that accumulate for that long. Continuously do small refactors to improve the structure.
Always spend at least 20% of the time on stuff you know is necessary, but will never be prioritized by marketing heads.
Don’t worry, it’s not like crucial decisions such as whether or not you get to keep your job depend on the outcome…
https://www.youtube.com/watch?v=8xRqXYsksFg
While the deadline for the previous task is also not pushed out.