Published in


Choosing the Right Agile Approach: A Guide to Scrum and Kanban

Photo by airfocus on Unsplash


Kanban is a visual method for managing and optimizing the flow of work. It was originally developed for manufacturing and is now commonly used in software development and other fields. Kanban boards typically represent work items as cards on a board, and use columns to represent different stages of a process. The goal of kanban is to limit work in progress and allow teams to focus on delivering value and continuously improving their processes.


Scrum is a framework for Agile project management and software development. It emphasizes collaboration, flexibility, and the delivery of working software through short, iterative cycles known as “sprints”. Scrum is based on several key roles, such as the Scrum Master, Product Owner, and Development Team, and defined ceremonies, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The goal of Scrum is to help teams deliver a high-quality product incrementally, with a focus on continuous improvement and adaptation to changing requirements.

What’s the difference?

Scrum and Kanban are both project and software management methodologies, but they have some key differences.

In Scrum, the main responsibilities of a person include:

  • Being a member of the Scrum team, which includes the Product Owner, Scrum Master, and Development Team.
  • Participating in sprint planning, daily stand-up meetings, sprint review, and sprint retrospective.
  • Helping to define and refine the product backlog.
  • Tracking progress and identifying any obstacles or issues that may arise during the sprint.
  • Communicating regularly with the Scrum Master and other team members to ensure the sprint goal is met.

In Kanban, the main responsibilities of a person include:

  • Understanding and following the Kanban process.
  • Helping to visualize the work and flow of tasks.
  • Managing and limiting work in progress.
  • Continuously monitoring and improving the workflow.
  • Communicating regularly with team members to ensure tasks are moving smoothly through the pipeline.

In Conclusion:

👋 Feel Free to Clap and Share your Thoughts!

Find more at our LinkedIn, Instagram, and Twitter. Check our podcast. Follow our LinkedIn page and Newsletter!



PM101 is a well-established blog that shares valuable content about product management. It has been receiving half a million visitors per year since 2016 and it’s free to access. PM101 has begun accepting guest posts, which allows other experts in the field share their insights.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Thaisa Fernandes

Product Management & Global Partnerships | Host @ Latinx in Power Podcast | Book Co-Author @ Mulheres de Produto