3 ms·
Unfortunately not all of us are blessed to work with well organized stakeholders who are able to plan ahead rather than wait until the last minute to request wh
by snorkel 13y ago
Unfortunately not all of us are blessed to work with well organized stakeholders who are able to plan ahead rather than wait until the last minute to request whatever they need from engineering. Agile only works when the entire organization abides by its rules, sure engineering teams can train their stakeholders to some degree but upper management can just overule the process and insist engineering should be like a service desk that responds to whatever is needed today. Sucks, but it's a reality in many workplaces.
- bdehaaff 13y agoSo what methodology have you found that works well in that environment? I am curious what helps you manage the madness as best you can when PM is not organized and "management" meddles.
- bhattisatish 13y agoI agree. That's the reason I love Kanban. It allows us to capture metrics on what is being done, how long it took and where are we spending most of our time. This numbers in turn allow us to push the story to management on what they are doing wrong. For e.g. We worked on a team where Sales made a feature request (1 day, PM and design team worked on it and released it to engineering (5 weeks) and engineering released it to sandbox (2 weeks), qa tested it and released it to production (1 week). Guess where the bottleneck is? The whole cadence for the feature was 8 weeks. Obviously Sales where jumping on us for not getting it done on time. This way of looking at the whole board, allowed us to identify a bottleneck and push for changes on how the whole company operates. If you kanban a board only for engineering then you lose the big picture, How is the system as a whole operating.