Agile software development

Simone Kohl

2 mins read

The goal of a software developer and the development team is to offer the customer the greatest possible benefit. First of all the purpose of agile principles is to help teams to focus on their goals using simple techniques.


The computer scientist Kent Back and his team created the theoretical basis for agile software development in 1999. They formulated the “Agile Manifesto” in 2001, it contains the principles of agile software development.
Above all this form of software development differs from the classical model, because the focus is on functionality and the user. The Agile Manifesto consists of 12 principles about this we have already written a blogpost: Additional principles for agile project management

Scrum Development

Scrum is about developing projects over a series of sprints. At the beginning the Scrum Master does a planning session. In this session the team members get a list of tasks and they decide how many tasks and which tasks can be completed in the sprint.
Therefore the team members complete the tasks during the sprint. Daily Scrums are held every day, where everyone has the opportunity to report on obstacles and compare their work with the other team members.
At the end of the sprint there is a Sprint Review where feedback can be given and new functionality can be demonstrated.

The most important artifacts

First of all the most important artifact in Scrum is the product itself. In Scrum, the team should bring the product to a potentially deliverable state at the end of the sprint. In the end the backlog contains the complete functionalities that still have to be added to a product.

The most popular way of creating the backlog is with the user stories. These are short descriptions of the functions.

Other artifacts are the Sprint Burndown diagram and the Release Burndown diagram. The Burndown Diagram shows the remaining workload in a Sprint. It helps to determine if the schedule can be kept.

Final thoughts

With the agile way of working, it is possible to respond flexibly to the wishes of the customer. And also to minimize the risks in the development process.

Share this article

Article by:

Simone Kohl
Simone Kohl

Share this article