About our sprint 0

Our sprint 0 is an important part of our working method and development processes. In order to know why, what and for whom we are developing, we like to focus the first few weeks on researching and deepening important information about the project.

This sprint 0 consists of a number of phases, where we slowly move from research and general wishes to concrete definitions and software requirements. In this process we will often also work closely together to obtain the right information. At the end of the process, everyone has a clear picture of what will be developed and everyone is on the same page.

To make this process as simple as possible, we have developed a sprint-0 toolkit. This is an overview of all possible activities that can be performed during sprint 0. We make a selection of these activities especially for you, depending on whether it concerns a new product, an innovation process or the digitization of processes.

We close the sprint 0 with an extensive and transparent report of our results. This document contains all the information needed to start the development process. Get a quote for the development of the MVP.

An overview of all losing parts of our Sprint-0s

Phase 1: Understanding & Research

It is important that we as your development partner understand the context of your project. In addition to technical research, the business context of the product is also important. That is why we like to delve into your wishes and goals and the needs of your end users and stakeholders.

the largest part of the sprint 0 consists of this first phase, where we have the right information collecting through interviews and research. We have enough information, this section will be concluded with an overview of business, user, stakeholder and technical requirements.

Contextual Research

This is an exploratory study to get a first picture of the context of the project.

Business processes

We monitor your business processes and, where possible, provide suggestions based on our experiences. Later we help translate these into software that is tailored to your KPIs and wishes.

User research

We make a careful overview of the requirements and wishes of your users. We include these in the development, or if necessary, in the design of the concept.

Stakeholder research

We make a careful overview of the requirements and wishes of your stakeholders. We include these in the development, or if necessary, in the design of the concept.

Technical research

What systems are there? Which links should be made? What data is there?

We bundle our research into an overview of business, user, stakeholder and technical wishes for the product.

Phase 2: Thinking & Concept development

Sometimes there is a lack of translation between your wishes and a concrete product proposal. We help you to realize our ideas and are happy to give advice based on our expertise.

Often we also make a visual approach (sketch/prototype) of the end product by means of wireframes or mockups, to give you and your customers as well as ourselves an idea of the end product.


We like to think along with your product. We are experienced in brainstorming and bundling from a proposal that is correct from both a technical user perspective.

Refine and Iterate

We ensure a good balance between research and concept development. If necessary, we make several effective layers of research so that we come up with the right solutions

Sketching and Wireframing

The first sketches and wireframes of a product help to form a common picture of the scope and direction of the project.

Concept Validation

We are happy to help with the assessment and testing of your concept. Our internal UX team is experienced in conducting evaluative tests and can help propose substantiation.

Turnkey Solutions

In those cases, you already have a piece of software in mind. We are happy to help you make the difference between your wishes, existing software and custom builds.

We bundle all requirements and wishes and create an overview of functional requirements that your product should contain.

Phase 3: Decide & Define

As soon as there is a clear and concrete picture of the end product, we start explaining all aspects and of the system.

Think, for example, of developing the software architecture, determining programming languages and making a workable demo for testing and as a reference for the frontend.

We conclude this section with an MVP (minimum viable product) definition. This is a tactically stripped-down version of your product that we will iteratively expand. With this we can guarantee that your product actually meets your wishes and those of your stakeholders.

Optimization, AI & Machine Learning

Our data scientists are looking at the possibilities of applying machine learning from AI to your data. If desired, we give advice on possible steps that can be taken.

Mockups and Demos

We make an extensive sketch of the most important elements of the material. If desired, we can already make a prototype or demo for your customers of users.

Data, privacy and regulations

Our products are delivered in accordance with the AVG law and other security standards. If desired, we determine whether additional measures are necessary. So you are always sure of a safe.

Software architecture

We set up the architecture that your system will use. This is a complete overview of all components, equipment, couplings and their infrastructure.

Technology and tools

We make one between all possible languages, frameworks, and decide which ones to use for the development of your product.

We determine the scope of the MVP by prioritizing the functional requirements. This is the first focal point of the development. In any case, you are guaranteed a functional product.

Phase 4: "Preparing for Takeoff"

With the MVP definition we are ready to start development. Before we start, we make an extra check with our internal tech board team, we make a ‘final scope’ definition, and we make a proposal for planning and dividing our roles.

In addition, you will receive a quotation for the development of the MVP, including a fully detailed and transparent document with all future information that we have collected during the sprint 0. This document is the blueprint of the project and contains all the information needed for development.

Tech Board Review

To ensure that our proposal is absolutely correct, we conduct an internal review with our Techboard. This is a team consisting of all lead developers, who once again critically review all progress and decisions.

Planning & Roles

The Project Manager, Product Owner, Lead developer and Lead UX are determined. In addition, we look for the right developers with the right skills, and we ensure that space is kept free in the planning.


You will receive a complete and transparent document with an overview of all documents and data that we collected during the sprint 0. This document also contains all the information necessary to proceed with development.


You will receive a quote for the development of the MVP. This quote is entirely based on the expenses we collected during the sprint 0.