Agile Project Management with SCRUM
(→Abstract) |
(→Abstract) |
||
| Line 4: | Line 4: | ||
First agile project management (APM) methodologies are created and implemented in the early 1990s, especially for IT projects, mainly cause of the fast-changing project environment. In the manifesto of agile software development, the following key values for APM are defined: " Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan" <ref name=''Mannifesto for Agile Software Development''> ''Agilemanifesto.org'' </ref>. | First agile project management (APM) methodologies are created and implemented in the early 1990s, especially for IT projects, mainly cause of the fast-changing project environment. In the manifesto of agile software development, the following key values for APM are defined: " Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan" <ref name=''Mannifesto for Agile Software Development''> ''Agilemanifesto.org'' </ref>. | ||
| − | The overall goal is to reduce complexity in the development of projects, to support a quick implementation in an inexpensive and high-quality way according the customer needs. The SCRUM agile project management approach is the dominant methodology used in the practical context and was introduced by Nonaka and Takeuchi in their "new product development Game". It is designed to guide team in the iterative and incremental delivery of a product. In | + | The overall goal is to reduce complexity in the development of projects, to support a quick implementation in an inexpensive and high-quality way according the customer needs. The SCRUM agile project management approach is the dominant methodology used in the practical context and was introduced by Nonaka and Takeuchi in their "new product development Game". It is designed to guide team in the iterative and incremental delivery of a product. In the following article the overall SCUM process is described with its roles, meetings and rules. In addition, a comparison between the traditional "old-school" project management approach and APM is executed and the benefits as well as limitations of the SCRUM methodology are discovered and critical analyzed. |
== References == | == References == | ||
<references /> | <references /> | ||
Revision as of 10:03, 12 February 2018
Abstract
First agile project management (APM) methodologies are created and implemented in the early 1990s, especially for IT projects, mainly cause of the fast-changing project environment. In the manifesto of agile software development, the following key values for APM are defined: " Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan" [1].
The overall goal is to reduce complexity in the development of projects, to support a quick implementation in an inexpensive and high-quality way according the customer needs. The SCRUM agile project management approach is the dominant methodology used in the practical context and was introduced by Nonaka and Takeuchi in their "new product development Game". It is designed to guide team in the iterative and incremental delivery of a product. In the following article the overall SCUM process is described with its roles, meetings and rules. In addition, a comparison between the traditional "old-school" project management approach and APM is executed and the benefits as well as limitations of the SCRUM methodology are discovered and critical analyzed.
References
- ↑ Agilemanifesto.org
