Prioritization

Team members work with a product manager or project manager to make sure the stories in the backlog and other status columns are prioritized and that work continues to move forward toward completion. The product manager is still responsible for ensuring the customer’s voice is heard and the product moves in the correct direction.

Kanban whiteboard

Limit work in process

One unique aspect of Kanban is that teams have a limit on their capacity for the amount of stories they can handle at any given time. Teams choose a certain amount of stories that they are willing to have in their “to do” and “in progress” columns, and they don’t go over that number in order to prevent burnout. Once a story is moved to “complete,” a story from the backlog takes its place in the “to do” column.

Continuous improvement

Kanban allows for continuous improvement by providing a system for teams to measure their effectiveness. They can clearly see how their work flows operate, how long every piece of the workflow takes, and how often they are getting their deliverables out the door on time. This makes it easier to experiment with different ways of doing things to optimize output.

Previous pageWhat is the Scrum methodology and how does it work?
Next pageTransitioning to Agile

Workfront