article thumbnail

Agile vs Waterfall: What’s the Difference?

ProjectManager.com

In 2001, a group of 17 software developers got together in a resort in Utah, and together came up with the “ Manifesto for Agile Software Development ” as a reaction to what they deemed as heavy project management methodologies—like waterfall. Even though agile is popular, the history of agile is in its infancy. Benefits of Agile.

Agile 395
article thumbnail

Agile and Current Technology: Are We Adapting or Missing the Mark?

Leading Agile

Agile officially began with the Manifesto in 2001 and was designed to: Empower developers. Remember, in 2001, people were still getting started with personal computers, and though they were becoming more and more common in households, not everyone had one. To achieve sustainable Business Agility, you have to change the system first.

Agile 131
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Risk Management Resources

Herding Cats

Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. Risk Management is essential for development and production programs.

article thumbnail

The Growth of Value-Driven Project Management

International Institute for Learning

The result was the creation of one of the world’s first project management maturity models and was published by John Wiley & Sons in 2001. [1]. A greater acceptance of risks, especially business risks, that may not have been fully understood at project approval. 1] Kerzner, Harold (2001).

2001 78
article thumbnail

The Agile Manifesto from a Lean Perspective

Scrum.org

So where were you between February the 11th and 13th, 2001? Any non-conformances with stakeholder expectations can then be exposed and dealt with rapidly, and the risk of effort being wasted on unproductive activities is minimized. Agile processes promote sustainable development.

Lean 148
article thumbnail

5 Agile Methodologies for Project Managers that are not Scrum Framework

Project Pulse Journal

Beck, facing the challenges of a high-risk project with dynamic requirements, sought to improve the software development process and practices, leading to the creation of XP. Risk Management – Integrating risk management from the outset is vital. 2001, December). References Kanban Tool by Shore Labs. ComputerWorld.