Sprint 0 Methodology

Good preparation is half the battle. Especially in software development, this is of great importance. Performing a Sprint 0 ensures that the development, which may follow, can be realized in a manageable manner without any major surprises.

Agile working has many advantages that Recognize applies successfully. The flexibility offered by the two-week rhythm during development sprints allows us to make adjustments during the process. Before we actually start sprinting, we also find it important to map out with our clients why we are pursuing something, how we are going to do it, and what we are working towards. This benefits the quality and speed during the development sprints while minimizing unnecessary detours or wrong turns. It is also important that expectations regarding the end goal are clear and consistent for all involved.

Sprint 0 Methodology
The deliverables
Product Vision Board

The product vision board describes the product vision and strategy. This is where the target audience, needs, product, and goals are addressed.


The storymap is a graphical representation of the product backlog. The storymap provides an overview of the components and requirements.


The architecture provides an overview of the application components and linked systems.


The prototype gives an impression of what the solution will look like. The prototype contains the main screens of the application.

The Sprint 0 process ensures that the business case can be soundly qualified relative to the investment required. The Sprint 0 sessions focus on the creation of the four deliverables. The functionality is worked out at the appropriate level and will be estimated item by item. The system architecture will be designed and tested against the existing and future IT landscape. All these elaborations become visual and “tangible” through the prototype that will be delivered. The prototype is in the form of a clickable design or a working basic application.

It regularly happens that certain components have been developed earlier or are available in the market. If it seems opportune to give this attention so that the development scenario will be more favorable, a make-or-buy analysis is performed for this. This is performed prior to working out the architecture and prototype. Sometimes buying is more favorable, faster, or cheaper than making it yourself. In addition, we are not advocates of reinventing the wheel. We either apply proven technology or concepts or make them better.

How does the
sprint 0 methodology work?

Typically, four to six half-day sessions are required to execute Sprint 0, during which Recognize’s team facilitates interviews to uncover the needed requirements, information, and frameworks and then develops and delivers them after these sessions.


Each session will require different experts from the client. The first session will focus on arriving at the Product Vision Board, and a broader composition of stakeholders is needed during this session. In the Architecture session, where the focus is on technology, IT landscape and data flows, different experts are again desired.


The Sprint 0 sessions focus on the creation of the four deliverables and take place through on-site sessions and/or video calls. The composition of the required team per Sprint 0 session is coordinated in advance of the session so that it is easy to plan for all parties.


Curious about what we can do for you? Or can you do something for us? Then we would love to hear from you! Feel free to call or mail. We are happy to come by to get acquainted. And of course, our doors on the seventh floor of the Javatoren in Almelo are always open.