|
|
|
|
|
by vundercind
667 days ago
|
|
I’m at a place that’s implementing it backwards: “let’s train everyone doing the actual work on all the ceremonies and how to waste a bunch of time dicking around in issue trackers… wait you’re missing every sprint goal badly, why? We better figure that out!” We could have told you why before any of this: tasks get dropped on us and we’re told to work on them without yet having the necessary access, context, a firm explanation of what actually needs to be done, often no idea who it’s for or who knows can answer the questions we have, et c. So we lose 1-2 two-week sprints figuring out a bunch of crap that the right people could have put together in a day or three, then get to actually start the development work. Getting that right should be table stakes before starting with all the ceremonies and shit. Fixing that is everything and doesn’t require “agile”. Do that and everything will work great. Agile will get the credit if we do ever fix that, but has nothing to do with it. [edit] oh and of course they’re paying external agile consultants for all this, further increasing waste. |
|