2 ms·
It's a lot of work to make it work smoothly, but I've done it at several places, so it absolutely can. :) Some notes: > Most business stakeholders will never b
by crazygringo 7y ago
It's a lot of work to make it work smoothly, but I've done it at several places, so it absolutely can. :) Some notes:
> Most business stakeholders will never be able to describe
That's what planning poker helps with. The engineers envision what they think business wants. Then you go back with the estimate and a description of what will be built, and they either sign off or say "that's not it at all!" The latter happens frequently. You may have to do a couple rounds of planning poker, especially in early days.
> 2 weeks is an eternity is a fast moving business.
I've never experienced that. What industry are you in? Obviously there are urgent exceptions, but when you take into account design, engineering, testing, and deployment, it's hard for me to imagine things taking less.
> estimates will be low by either a factor of 2 or 3
That's what the points estimation and sprint burndowns are for. After a few iterations, estimates become surprisingly accurate. (They never are at the start.)
> everyone else will take it as a promise
You need management's support for the process. And it takes a lot of communicating. 10x more communicating than you think it will.
The rest of it sounds like you work somewhere that's pretty toxic. And of course no process can fix that. But if you call your job chaos management, I highly recommend looking for a new job. ;) That happened to me as well at one unfortunate job...