By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
PreferencesDenyAccept
Insights
#innovation

How we do Agile development

Anyone can benefit from an Agile development method. After all, this is a fast, step-by-step way of development with a fixed structure. Via Agile development you can make quick adjustments via short lines of communication and thus significantly reduce the development time. But what exactly does that method entail?

Solid architecture

‍

First of all, we start a project by drawing up the blueprint of the web application, during the so-called architecture phase. This takes about two to five days, after which we start developing the software.

The development via the agile method takes place in sprints, which are short periods in which the pre-agreed functionalities are worked on. The duration of a sprint is ten working days, or two weeks. A sprint has a fixed structure, which we always adhere to.

‍

Kick-off

‍

On the first day of the sprint, we hold a kick-off meeting, in which we go over the various functionalities of that sprint and check whether all details are clear. This way, both the development team and the customer know what the expectations are for the next two weeks.

Then there are seven days to develop whatever is on the development schedule. Login screens, integrations (connections between different applications to link them), an interactive map, ... An endless number of functionalities are possible, which are therefore extensively tested by our development team.

‍

"Thanks to short cycles, clear agreements and a fixed structure, both the development team and the customer are and remain satisfied."

‍

‍

Retrospective

‍

On the last Friday of the sprint, it is time for the demo of the built functionalities and a retrospective. In this we collect feedback from the customer, which we will use in the upcoming sprint period.

‍

UAT

Then it is up to the customer to test, which we call 'user acceptance testing', or UAT for short. During UAT, the customer will test the functionalities and accept or provide feedback. At the same time that the customer is busy with UAT testing, our development team starts developing the next sprint.

In this way we keep the lines of communication short, adjustments can be made in no time and projects progress quickly. Thanks to short cycles, clear agreements and a fixed structure, both the development team and the customer are and remain satisfied!

Are you curious what we can do for your project? Reach out and we tackle your challenge together.

‍

‍

Other insights

#innovation

Customer Behaviour Analysis

A 'customer behavior analysis' may sound complicated, but the bottom line is that what you do online as a customer is mapped. And that in turn leads to interesting and substantiated insights into your market.
Lees meer
#innovation

A hub with endless possibilities: the dynamic API layer

Fortunately, digital business operations have already become implemented in many organizations. Companies have been working for longer than today with multiple programs that make life better for their customers and themselves. In my opinion, the real added value lies in connecting those tools, both internally and externally. A true digital ecosystem. But before you can get started, you need an intermediate piece: a dynamic API layer.
Lees meer

Do you want to work with us?

Contact us