The early years of software development were characterized by a growing number of software companies that developed and introduced products through unplanned and lengthy processes. Using these old processes and approaches to deliver products to end users can take months or even years.
The frustration with old project management techniques pushed software providers to find effective and fast ways to introduce new products and features into the market. To achieve this goal, 17 developers – aka the Agile Alliance – met at The Lodge at the Snowbird Ski Resort in Utah on February 11–13, 2001. The outcome of the meetings was the development of the Agile Manifesto. The manifesto consists of four main values and 12 principles that put collaboration, human interaction, efficiency, quality and client needs at the forefront of the methodology. Additionally, Agile was designed to significantly reduce the time spent developing new software versions and releases by adopting short periods of work also known as sprints.
|Criterion||Old project management approach (e.g. Vee model, spiral model, waterfall model)||Agile approach (e.g. Scrum, LSD, Kanban, FDD)|
|Development model||Life-cycle model||Evolutionary delivery model|
|Planning scale||Long term||Short term|
|Requirements||Defined at the beginning of the project||Adapts to evolving needs|
|Team size||Departments||Cross-functional teams|
|Interaction with clients||At the beginning of the project and at specific milestones||Frequent|
|Testing||At the end of the project||Continual testing|
|Documentation||Detailed and through||Only when needed|
( Your e-mail address will not be published)