---
title: How did the Agile Manifesto address the issues of traditional software development?
description: "The [Agile Manifesto](https://www.thescrummaster.co.uk/glossary/agile-manifesto/) was created in 2001. It was intended as a response to the heavyweight, documentation-driven software development processes that were in everyday use at this time. The manifesto is a set of values and principles. People interpret the…"
url: "https://www.thescrummaster.co.uk/docs/how-did-the-agile-manifesto-address-the-issues-of-traditional-software-development/"
updated: "2024-12-19"
category: Introduction / What Is Agile?
---

# How did the Agile Manifesto address the issues of traditional software development?

The [Agile Manifesto](https://www.thescrummaster.co.uk/glossary/agile-manifesto/) was created in 2001. It was intended as a response to the heavyweight, documentation-driven software development processes that were in everyday use at this time.

The manifesto is a set of values and principles. People interpret the meaning of these values and principles through their own life experiences, interests and biases. As a result, it means very different things to different people. I typically get ten other answers when I ask ten people what Agile is. Despite this, taking an Agile approach is now the default way to develop products for most organisations today. However, transitioning to a new approach can be hard, and the benefits of adopting Agile must outweigh the cost.