by Aki Namioka, Senior Agile Consultant
When an organization is deciding how to manage the work of an Agile team, two common paradigms are often considered: Scrum and Kanban. This article will discuss each paradigm at a high level, cover the advantages of each, and explain why a team might select one or the other.
Introduction to Scrum
Scrum’s history comes from software development. It has been around, in some form or another, since 1986 and is the most common Agile paradigm in software development. The current definition of Scrum was presented in 1995 by Ken Schwaber and Jeff Sutherland. It is described as “a flexible, holistic product development strategy where a development team works as a unit to reach a common goal.”
At Scrum’s core is the idea of working in iterations or “Sprints”, where a cross-functional delivery team works together to meet a set of goals that are defined by a Product Owner, i.e. somebody who can represent the business interest. A Sprint is a time box, e.g. 2 weeks. At the end of each Sprint, the delivery team demonstrates incremental business value to the Product Owner. Read more