A brief history of the agile methodology Last Updated : 26 Mar, 2024 Comments Improve Suggest changes Like Article Like Report History of AgileIn 1957, people started figuring out new ways to build computer programs. They wanted to make the process better over time, so they came up with iterative and incremental methods.In the 1970s, people started using adaptive software development and evolutionary project management. This means they were adjusting and evolving how they built software.In the 1990s, there was a big change. Some people didn't like the strict and super-planned ways of doing things in software development. They called these old ways "waterfall." So, in response, lighter and more flexible methods showed up. These included: Rapid Application Development (RAD) in 1991.Unified Process (UP), Dynamic Systems Development Method (DSDM) in 1994.Scrum in 1995. Crystal Clear and Extreme Programming (XP) in 1996. Feature-Driven Development (FDD) in 1997. Even though these came before the official "Agile Manifesto", we now call them agile software development methods. In 2001, seventeen software developers met at a resort in Snowbird, Utah to discuss lightweight development methods. They were: Kent Beck (Extreme Programming), Ward Cunningham (Extreme Programming), Dave Thomas (PragProg, Ruby), Jeff Sutherland (Scrum), Ken Schwaber (Scrum), Jim Highsmith (Adaptive Software Development), Alistair Cockburn (Crystal), Robert C. Martin (SOLID), Mike Beedle (Scrum), Arie van Bennekum, Martin Fowler (OOAD and UML), James Grenning, Andrew Hunt (PragProg, Ruby), Ron Jeffries (Extreme Programming), Jon Kern, Brian Marick (Ruby, TDD), and Steve Mellor (OOA). They wrote something important called the Manifesto for Agile Software Development. This was a big moment that set the stage for the agile movement. In 2005, Alistair Cockburn and Jim Highsmith added more ideas about managing projects, creating the PM Declaration of Interdependence. Then, in 2009, a group, including Robert C. Martin, added principles about software development. They called it the Software Craftsmanship Manifesto, focusing on being professional and skilled.In 2011, the Agile Alliance, a group of agile enthusiasts, made the Guide to Agile Practices (later called Agile Glossary). This was like a shared document where agile people from around the world put down their ideas, terms, and guidelines. It's a bit like a dictionary for how to do agile things. Comment More infoAdvertise with us K kashishkumar2 Follow Improve Article Tags : Software Engineering Similar Reads Scrum methodology in Software Engineering Scrum is the best Agile practice in today's world. This article includes all the concepts regarding product backlog, team role, sprints, burndown charts, and more. Agile moto is “Build short, Build oftenâ€. Scrum is using agile methodology, rather than viewing it as a methodology, think of it as a fr 3 min read What is a User Story in Agile? The user story is a natural language-based and informal way of specifying one or more requirements of software and product development. A user story is usually used in the agile model to describe from the end user's perspective which can ultimately help us create a simplified description of the requ 5 min read Agile Methodology Advantages and Disadvantages Agile Software Development Methodology is a process of software development similar to other software development methodologies like waterfall models, V-models, iterative models, etc. Agile methodology follows the iterative as well as incremental approach that emphasizes the importance of delivering 4 min read What are Software Development Methodologies | 15 Key Methodologies The main objective of Software Development companies is to provide high quality software products at low cost. Therefore, proper planning is required and proper management is required for the software development process. Thus a proper methodology is important for achieving this type of objectives b 9 min read When to Use Agile Model? In the Agile model, the focus is given to process adaptability and customer satisfaction. In earlier times, the iterative waterfall model was used to create software. But in today's time, developers have to face many problems. The biggest problem is that in the middle of software development, the cu 5 min read Scrum for Agile Product Management Teams Scrum for Agile, is a dynamic and collaborative framework, has emerged as a cornerstone for Agile product management teams seeking effective ways to navigate the complexities of modern software development. Designed to enhance flexibility and responsiveness, Scrum for Agile provides a structured app 9 min read Like