Scrum in the context of lean and agile project management
Abstract
Scrum is originally an iterative and incremental agile software development procedure model to manage the product development process. [1] Even though Scrum was developed as an agile software development framework, it developed since the 1990's to a general project management method. [2]
Scrum was mentioned for the first time in the Harvard business Review article “New New Product Development Game” from 1986. In this article Takeuchi and Nonaka compared the work processes in high-performing and cross-functional teams with the scrum formation used in Rugby. [3]
Scrum is based on three pillars [4]:
1) Transparency
2) Inspection
3) Adaption
As Scrum is an agile approach it is close connected to the agile movement. The agile movement is summarized in the “agile manifesto” (2001), which states: “Individuals and interactions over processes and tools;
Working software over comprehensive documentation;
Customer collaboration over contract negotiation;
Responding to change over following a plan”. [5][1]
This article will explain Scrum as a project management method in relation to the agile movement. Moreover, this article puts Scrum in the context of lean project management. Scrum with its independent origin from the Toyota production system, is not a transfer of Toyota production methods to project management.
Scrum is an agile frame work, which allows to execute product development or projects in an iterative, incremental way. [6]
Contents |
Scrum
Scrum is originally an iterative and incremental agile software development procedure model to manage the product development process. [7] Nowadays, Scrum is the most widely adopted agile project management methodology and is IT industry independent.
Scrum methodology is based on empirical process control theory. Empiricism assumes that knowledge is gained from experience and decision making is made on known knowledge. Therefore, Scrum is an circular and incremental methodology following the goal to optimize planing capability and control risk.
In connection, Scrum is based on same three pillars as empirical process control: transparency, inspection and adaption .
Furthermore, is Scrum based on specific Scrum Roles, Scrum Events and Scrum Artifacts, which are determined and cannot be skipped.
History of Scrum
Three Pillars of Scrum
Scrum Roles
Scrum Building Blocks
Scrum Documents
Agile Methodology
Agile Methodology and Scrum in Practice
Scrum in the context of Lean Project Management
- ↑ "What is Scrum?". What is Scrum? An Agile Framework for Completing Complex Projects - Scrum Alliance. Scrum Alliance. Retrieved 24 February 2016.
- ↑ "Mary Poppendieck, Tom Poppendieck: Lean Software Development: An Agile Toolkit", Addison-Wesley, Upper Saddle River, 2003.
- ↑ "The New New Product Development Game“. Cb.hbsp.harvard.edu, 1. Januar 1986.
- ↑ "Ken Schwaber and Jeff Sutherland: The Scrum Guide", 2016.
- ↑ http://agilemanifesto.org
- ↑ Pete Deemer; Gabrielle Benefield; Craig Larman; Bas Vodde (December 17, 2012). "The Scrum Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0). "A"
- ↑ "What is Scrum?". What is Scrum? An Agile Framework for Completing Complex Projects - Scrum Alliance. Scrum Alliance. Retrieved 24 February 2016.
Cite error:
<ref> tags exist, but no <references/> tag was found
