Agile Manifesto
17 software development gurus held a 2-day meeting in the United States in 2001. Before the Agile Manifesto that offered with this meeting, 17 software development masters who attended the meeting were trying to find their own solutions to the problems they experienced in traditional methods individually.
They published the Agile Manifesto at the end of the 2-day meeting. The Agile Declaration consists of 4 values and 12 principles.
Çevik Değerler
Çevik Prensipler
Why Agile?
According to The Standish Group's Chaos Report, which was created with the follow-up of more than 10,000 projects in 2015; software projects progressed with Agile practices failed at a rate of 9%, while projects managed with Waterfall failed at a rate of 29%.
In the same report, the primary reasons for the failure of the projects are listed as follows:
- Unclear/incomplete requirements
- Changing requirements
- Lack of resources
- Unrealistic expectations
- Lack of management support
- Excluding user from the project

The requirements of today's world change rapidly; technology changes, customers change, market conditions change, requirements change, the financial situation changes, competitors change… in brief, everything changes.
Therefore, it is highlighted in the Agile Manifesto that responding to change is more significant and prior rather than adhering to a plan. When Agile practices are applied, in addition to being able to respond quickly to change, early detection of risks due to its iterative approach increases quality and shortens the access time to market. Productivity increases consequently.