Skip to main content

Agile software development

Agile software development describes a process through which the writing of appropriate solutions should succeed faster and easier. The development also runs iteratively. This is a process in which identical or similar processes are repeated several times in order to get closer to a solution.

In the field of agile software development, for example, those involved repeatedly sit down and consider what features the software should have in order to be particularly customer-friendly. Agile means something like agile. Software development should no longer be constrained by rigid structures, but should unfold freely in the form that leads to the best result.

How does agile software development work in concrete terms?

When agile software development is to be used in companies, the Agile Manifesto, which was published in 2001 and written by the US-American researcher Kent Beck and his team, is usually used for the introduction. It marks the beginning of agile software development and presents twelve central principles. These focus on the customer and their needs. Development must subordinate everything to the goal of delivering the perfect result. To achieve this, those involved in the project should work together as intensively and closely as possible – face to face.

Classic methods for agile software development are Scrum and Kaban.

  • At Scrum, there is no need for a project manager. Instead, developers are given as much freedom as possible in their day-to-day work.
  • Kaban relies on extensive visualization to create transparency. Maps, graphs and diagrams are used to record what has already been achieved and how things are progressing.

The glossary article on Agile UX might help you:

To the article

Do you have any more questions?

Please contact us


Further contents