If you don’t know where you are going, you don’t need a map. During plotting, we learn to understand your problem and identify what you need from the product. Plotting is done in short daily workshops and is open to anyone who needs to attend. An amount of 2 weeks is allotted for this phase.
Plot the course
1
Leave port
2
Traveling the high seas
3
Arrive at destination
4
Plot the course
1
Business case
We make sure that we understand our business case first.
We are running Business Case workshops so we can gauge the problem space. By the end of the workshops, we will have a detailed picture of the users’ needs and the specific KPIs the product has to achieve.
2
Transactions
Transactions describe how to solve a specific business problem. We map those transactions to make dependencies visible and define the scope of an iteration.
3
Surfaces
Together we model all of the surfaces required for your users. Starting with the interaction surface, we work on modeling all of the surfaces required for the users. Expensive Integrations are delayed to the last moment.
4
Capability body
In this phase, we detect the capabilities required to quickly get you started. Functionality for the surface is contained within the capability body.
5
Alignment
Various MVPs are generated in the very early stage with the goal to validate your ideas and strengthen the support. This phase might include not just technical MVPs, but also sales flyers, testimonials of the users, and fully functional prototypes as well.
Leave the port
With a plotted course we sail to the destination in less than 3 months. You will get a fully functional ready-to-use digital product built with you and adapted to your end-users. No paper prototype, no uncontrollable process – just a functioning Product.
1
Project iteration
Once the itinerary is clear our journey will start: In an increment of 6 weeks our crew works autonomously on their projects. Team progress is observable in real-time, without the need for daily interaction and supervision. 6 weeks of development are followed by 2 weeks for bug fixes. In case you wish we can insert various stops on the itinerary to do some sightseeing.
2
Features first
We work in features, i.e., we implement a feature from front-to-back and make it available to our users. We will use the interaction surface as the primary feature description.
3
All hands on deck
We will maintain contact with your end-users and keep them engaged throughout the project. We discuss features and make them testable to your end-users, without requiring them to be “tech-savvy”.
4
Seaworthiness and the first cargo
We develop everything right the first time and build on cloud technologies, so we can go directly from acceptance to production.
Traveling the high seas
Products improve over time. Going live with you is not the end of the project – it is the beginning of a great journey for you and us.
When the product is there we go full steam ahead
After 6 weeks the first iteration of the product is shipped
What is next?
We continue improving the product
We extend the product
We maintain the product
Arrive at destination
Once the product is perfect, the use-case is no longer relevant, or you pivoted your business on the product – a trip always ends.
At this stage, we can offer to you a few more follow-up scenarios: to put the product in development hibernation and run or to create an organization for further development together with you. The choice is yours.
