Agile Software Development Methodologies (SCRUM Vs KANBAN)

Scrum and Kanban are both iterative work systems (frameworks) that rely on process flows. While the practices differ, the principles are largely the same. Both frameworks will help you build better products (and services)  However, there are a few main differences between the two.

SCRUM

Roles:  Product Owner, Scrum Master, Development Team, Stakeholders

  1. Scrum Teams work in a series of Sprints of 2 (most common), 3 or 4 weeks duration.
  2. Scrum Master job is to help the Product Owner, the Development Team to develop and remove any Impediment.
  3. Sprint Planning Meeting: Each Sprint starts with a – facilitated by the Scrum Master and attended by the Product Owner and the Development Team and (optionally) other Stakeholders. Together they select high priority items from the Product Backlog that the Development Team can commit to delivering in a single Sprint. The selected items are known as the Sprint Backlog.
  4. The Development Team works on items in the Sprint Backlog only for the duration of the Sprint. In all but exceptional circumstances, new issues must wait for the next Sprint.
  5. The Daily Scrum (aka Daily Huddle, Daily Standup) is a short standup meeting attended by the Scrum Master, the Product Owner and the Development Team.
  6. Sprint Review: A review of the Sprint. Often includes a demo of new features to Stakeholders.
  7. Sprint Retrospective: A look at what went well, what could be improved, etc. Aim: to make each Sprint more efficient and effective than the last.
  8. At the end of the Sprint, completed items are packaged for release to live. Any incomplete items are returned to the Product Backlog.

KANBAN

Roles: Product Owner, Agile Coach, Development Team, Stakeholders

  1. Kanban is a continuous process. (vs. Scrum’s periodic Sprint).
  2. It is the job of the AgileCoach to help the Product Owner and the Development Team to develop and remove any Impediment.
  3. Items are “pulled” directly from the Product Backlog.
  4. Each column has a strict Work in Progress limit. This limits ensure that items move across the board in the shortest possible time.
  5. The Daily Standup is a short standup meeting attended by the Agile Coach, the Product Ownerand the Development Team.
  6. Each item is packaged for release as soon as it is ready.
  7. Demo: A demonstration of new functionality to Stakeholders.
  8. Retrospective: A look at what went well, what could be improved, etc. Aim: to improve the process.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s