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."
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.
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.