Agile software development for better products and satisfied customers

Imagine going on a sailing trip where you plan and prepare everything in detail before starting. You will find that once you've started you will face lots of situations to which you have to adapt. In this case you need to be flexible.

Software projects have a lot in common with a sailing trip. You cannot anticipate every eventuality in advance. Unforeseeable events often include changing requirements or a changing environment. However, traditionally managed software projects expect this kind of detailed planning to be able to start.

In contrast to traditional approaches, agile software development offers the required amount of flexibility to reach the customers goals efficiently. The realization can start even if the path to final product is still blurry. Agile projects are characterized by an iterative development process and a close cooperation between customer and product owner. This dynamic nature enables an immense degree of flexibility.

Benefits of the agile approach for the customer:

Higher level of flexibility

Short feedback loops enable changes and adjustments at any time. The customer can constantly monitor the project's status.

Time savings

Direct and close contact between customer and contractor minimize the risk of going into the wrong direction.

Gaining a competitive advantage

Reducing time-to-market because individual parts of the software can already be used before project finish.

Feedback loops are a crucial part of the agile development process. Every step of an iteration builds upon the preceeding one. Below you can see the different stages of one iteration of our agile development process.

Phase One:
Your part

You give us the 'raw' requirements. What is the software supposed to do? How should it look like? When do you need it done?

Our part

We translate your requirements into a list of acceptance criteria. This list is then sliced down into manageable work packages.

Phase Two:
Our part

We estimate the workload required for the previously defined work packages. This estimation is based on state-of-the-art knowledge and prior experience.

Phase Three:
Your part

Based on our evaluation you declare which work packages should be prioritized for this iteration.

Phase Four:
Our part

We build the deliverable. Through automated testing tools like Sonarqube a high code quality is ensured at all time.

Phase Five:
Roll-out of new version

In an automated process the new version is rolled out. This only happens when all the acceptance criteria are met and all quality gates are passed.

If you have more questions don't hesitate to ask.

Ask a question