3 ms·
Impact mapping gives you that big plan without having to detail implementation and keeps it manoeuvrable. Kanban lets you switch the backlog around through the
by dreamfactory2 12y ago
Impact mapping gives you that big plan without having to detail implementation and keeps it manoeuvrable. Kanban lets you switch the backlog around through the day and doesn't lock the project into sprints (which are mini waterfalls imo). Estimation is entirely optional here. (The main benefit I've seen from estimation is in forcing a dev team to collectively confront what's involved in implementing a feature - as an input not an output.)
- jacques_chester 12y agoI've found that Kanban leads to coordination overhead because you always have too much work in flight in too many stages. I prefer story-by-story development, which is the direction to which most Kanban implementations wind up evolving. One small thing, to completion, at a time, per pair.
- dreamfactory2 12y agoWIP limits should iron this out