Re:How does your team communicate/justify project delays to ...
by codingdave on Sunday October 11, 2020 @07:57AM
(#24745189)
"Responding to change over following a plan"
We don't give estimates for large, difficult projects. We do have a roadmap that is documented. We do decide what is next, and maybe lay out a month or two of a swag at what we'll get done, but mostly we just keep moving forward, delivering at a reasonable and sustainable speed.
Sure, leadership gets their own idea of what schedule we'll hit. And we often do meet their expectations. When it isn't correct, we tell them what stopped us from hitting it. But we do not approach such things as a "delay" - it is just how software dev works.
We don't give estimates for large, difficult projects. We do have a roadmap that is documented. We do decide what is next, and maybe lay out a month or two of a swag at what we'll get done, but mostly we just keep moving forward, delivering at a reasonable and sustainable speed.
Sure, leadership gets their own idea of what schedule we'll hit. And we often do meet their expectations. When it isn't correct, we tell them what stopped us from hitting it. But we do not approach such things as a "delay" - it is just how software dev works.