SCRUM Method
(→Introduction) |
(→Introduction) |
||
| Line 2: | Line 2: | ||
SCRUM is a one of the most used agile methodologies focusing on organizing and project management. The method’s foundation inheres the commercial product development work in 1986 elaborated by Hirotaka Takaeuchi and Ikujiro Nonaka and officially defined in a paper written by Jeff Sutherland and Ken Schwaber in 1995. The Agile Manifesto for software development published 1991 broadened usage of the technique aiming to continuous development of valuable software. | SCRUM is a one of the most used agile methodologies focusing on organizing and project management. The method’s foundation inheres the commercial product development work in 1986 elaborated by Hirotaka Takaeuchi and Ikujiro Nonaka and officially defined in a paper written by Jeff Sutherland and Ken Schwaber in 1995. The Agile Manifesto for software development published 1991 broadened usage of the technique aiming to continuous development of valuable software. | ||
| − | The key aspects addressed in the Agile Manifesto are: | + | The key aspects addressed in the Agile Manifesto: [http://agilemanifesto.org/principles.html] are: |
*Individuals and interactions over processes and tools | *Individuals and interactions over processes and tools | ||
Revision as of 16:12, 21 September 2015
Contents |
Introduction
SCRUM is a one of the most used agile methodologies focusing on organizing and project management. The method’s foundation inheres the commercial product development work in 1986 elaborated by Hirotaka Takaeuchi and Ikujiro Nonaka and officially defined in a paper written by Jeff Sutherland and Ken Schwaber in 1995. The Agile Manifesto for software development published 1991 broadened usage of the technique aiming to continuous development of valuable software.
The key aspects addressed in the Agile Manifesto: [1] are:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following the plan
SCRUM can be implemented to different projects aligning continuous requirements’ changes and strict deadlines. The aim of Scrum is to enhance teamwork, provide transparency, and optimize complexity of the projects and unpredictability of software development.
