4 ms·
We tried kanban with a few teams at my last startup. It worked great for a team with a clear direction, but was really hard from a management/planning/accountab
by jacobr1 4y ago
We tried kanban with a few teams at my last startup. It worked great for a team with a clear direction, but was really hard from a management/planning/accountability standpoint. It didn't mesh well with the quarterly planning cycle the rest of the company aligned on. So we took some of the key tools (like WIP limits) but otherwise moved to scrumban type process. It was a bummer, because we had some solid data on increased productivity, but couldn't really deliver increased predictability (not that scrum was more predictable in-practice, it just seems that way)
- koreth1 4y ago> (not that scrum was more predictable in-practice, it just seems that way) I use the phrase “the illusion of predictability” a lot when I talk about Scrum. Sadly, some people really cling to that illusion despite overwhelming evidence that it isn’t real.
- urthor 4y agoKanban isn't an externally facing interface. Quite honestly Scrum and story mapping isn't that good for a whole of company approach. You need to use tools like OKRs and good old waterfall to manage multiple team projects.