Agile Project Management with SCRUM
(→Big Idea) |
|||
| Line 10: | Line 10: | ||
===SCRUM Process=== | ===SCRUM Process=== | ||
| + | |||
| + | |||
=== SCRUM Roles === | === SCRUM Roles === | ||
Revision as of 18:04, 13 February 2018
First agile project management (APM) methodologies were 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. Furthermore, a key characteristic of APM is the high level of responsiveness to changes as well as continuous Stakeholder involvements over the whole project duration [2]. 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 SCRUM process is described with its roles, meetings and rules. In addition, a comparison between the traditional "old-school" project management approach and APM Scrum is executed and the benefits as well as limitations of the SCRUM methodology are discovered and critically analyzed.
Contents |
