4 ms·
My rule for deadlines is that it must have a “Why?” associated with it. Deadlines with a Why are real. Usually tied to an event outside of the dev teams control
by brightball 8y ago
My rule for deadlines is that it must have a “Why?” associated with it. Deadlines with a Why are real. Usually tied to an event outside of the dev teams control.
Anything that doesn’t have a Why next to it is essentially carrot dangling. You can have targets/forecasts when you expect to have something ready while making it clear that these are guesses, but if it’s not real then it creates real problems if you pretend that it is.
- t0mbstone 8y agoUsually the "Why" is always going to be some variant of, "The client wants this ASAP!", or "The client called and they are complaining about this bug". How would you force your manager into converting that "why" into one you would accept?
- brightball 8y agoWhen dealing with clients, ASAP = Rush Rate. If it’s really needed that fast, they will pay extra for it. If it’s not, they will wait for the timeline that you can hit. All that said, client work is the one place where sprints serve a real purpose. The scope doesn’t expand because you finish early so there is a built in reward, agreed upon price for the scoped work, and a built in penalty.