Agile methodology: Kanban VS Scrum

After a very comprehensive intro on Project Management methodologies where we explored Agile VS Waterfall, in today's post we are going to deep dive on some of the differences between Kanban and Scrum, two of the frameworks within the Agile framework.

While there are some clear differences between both practices, the principles are largely the same.

Scrum is a tool used to organise work into small, manageable pieces that can be completed by a cross-functional team within a prescribed time period called a “sprint” (generally 2-4 weeks long). To plan, organise, administer, and optimise this process, Scrum relies on at least three prescribed roles: 

-  The Product Owner, responsible for initial planning, prioritising, and communication with the rest of the company

- The Scrum Master, responsible for overseeing the process during each sprint.

- The Team Members, responsible to carry out the purpose of each sprint, such as producing software code.

Kanban is also a tool used to organise work for the sake of efficiency, and like Scrum, Kanban encourages work to be broken down into manageable chunks, however, where Scrum limits the amount of time allowed to accomplish a particular amount of work, by means of sprints, Kanban limits the amount of work allowed in any one condition as only so many tasks can be ongoing.

 In the table below you can find the main differences between Scrum and Kanban:

Finally the video below illustrates very clearly the differences and points out how the Scrum and Kanban boards work.

Until next time!