In our series on Plan-Do-Check-Act (PDCA), we began with PDCA as a general model for learning and improvement. Then we looked at Lean as a business application of PDCA, helping organizations maximize value and minimize waste. Our next step is Agile—a framework that brings these ideas into the world of software development.

What Is Agile?

Agile is not a single method but rather a mindset. It emphasizes flexibility, collaboration, and delivering value quickly. Instead of long, rigid development cycles, Agile promotes short, iterative cycles where teams can adapt to feedback and change.

The Agile approach is especially powerful in environments where requirements are uncertain or rapidly changing—common in software projects.

The Agile Manifesto

In 2001, a group of software developers created the Agile Manifesto, which outlines four key values:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

These values highlight the importance of people, communication, and adaptability in creating successful projects.

Agile Practices

Agile principles are applied through practices such as:

• Sprints: Short development cycles (often 1–4 weeks) that deliver working features.
• Daily standups: Quick team meetings to align on progress and obstacles.
• Retrospectives: Regular reviews where teams reflect and improve their process.
• Continuous delivery: Frequently releasing updates so users see value quickly.

Agile Compared to PDCA and Lean

PDCA provides a universal cycle for improvement. Lean applies PDCA to business processes, focusing on eliminating waste and maximizing value. Agile, in turn, builds on these foundations for the software world—where change is constant and customer needs evolve rapidly.

Agile is essentially PDCA in fast-forward, combined with Lean’s emphasis on delivering value. It encourages teams to “plan small, do quickly, check immediately, and act based on feedback.”

An Example of Agile in Action

Imagine a small software team building a new app. Instead of working for six months before releasing anything, they break the project into two-week sprints. At the end of each sprint, they deliver a working feature—such as a login page or dashboard—and gather feedback. This allows them to adapt their plans quickly and avoid wasted effort.

Closing Thoughts

Agile represents the software development step in our PDCA journey. By valuing adaptability and customer collaboration, Agile has transformed how teams build technology. It also sets the stage for future methods, such as PACE in data science, and even new cycles designed for artificial intelligence.