5 ms·

Kanban is an alternative to sprints, ... Agreed. ... for contexts in which the team is persistent across projects and it makes sense to let them manage th

Kanban is an alternative to sprints, ... Agreed. ... for contexts in which the team is persistent across projects and it makes sense to let them manage their work apart from the projects that they contribute Here I disagree only in applicability. Kanban can be successfully used in a single development project if the team maintains prioritized tasks based on risk and/or dependencies. To wit, a development team with sufficient maturity can identify and plan their work, address same in the requisite order, and have confidence that the probability of success will increase as each task is completed.

vannevar 4y ago
Prioritization is an output, not an input, of the scrum process. That's the whole point, to engage the user early and often so that information about the desired functionality can be derived from experience and not just speculation, and then fed quickly back to the team for iteration. So sure, if you: - release usable software - collect feedback from stakeholders based on the release, and - re-design and re-prioritize the perceived work remaining on a regular basis as a team, then you can use Kanban for a single project. But it will look an awful lot like sprints, because it's hard to do all that on a continuous basis, it would be a lot of overhead and context-switching to do it daily. On a project of any size, you'd have to do it all periodically. Say, every couple of weeks.