Wonder how we get from an idea to a working digital product in 30 days? It’s easy. We sprint it.
Digital world changes too fast to keep your product in the closet for months before you test it on the market – if that’s what you’re doing right now, you are doing it wrong!
You don’t want to invest a lot of money in something that simply won’t catch on and you most definitely don’t want to spend a year perfecting an idea just to see it launched by someone else before you do it. In today’s world, there’s only one way to keep up with the speed: you need to sprint.
If you thought that launching an MVP in 90 days was already speed of light fast, then brace yourself - we do it (and yes, we have done it before) in 30 days!
We start with the design sprint where we validate your assumptions and test the soundness of your business model. It’s an intense, collaborative process with the aim of answering critical business questions through design, prototyping and testing.
In a nutshell: the shortest possible way between coming up with an idea and collecting actual data and feedback.
Just a quick warm up. We start by looking at the bigger picture and mapping out the game plan: what is the problem we want to address, who are our user personas (potential customers) and what’s our product/market fit. Once we understand long-term goals of the project and do a business requirements analysis, we can pick a specific target to attack first.
Everyone gets together to come up with solutions to the target problem and challenge each other in a constructive way. We resort to the good old pen and paper and sketch out our ideas. We don’t just throw ideas at each other like at the usual brainstorming session, we pin them down and build up on them. Sometimes it gets crazy. Like Crazy Eights when we sketch eight solutions in eight minutes.
With a stack of sketches from the Generate stage, we’re at full speed now. We decide which solutions we want to prototype and make storyboards to walk us through the process. We build wireframes or even a “clickable” mockup of your dream application to visualise our ideas.
We roll up our sleeves and start building a prototype according to the storyboards prepared the day before. A prototype is a working web or mobile application that you could test with yoru clients.
The goal of the whole sprint is to test assumptions and draw conclusions. At the finish line, we bring the prototyped product to users and test their reactions. Some prototypes will be more successful than others, but all of them will tell us what to improve and what to keep and expand. We can now define a product roadmap and swiftly move on to building your validated product.
So now you have valuable feedback from customers, you have a product/market fit thanks to the prototype built in the design sprint and you have a list of features to implement in your new app. Thanks to cutting-edge technology we use like Node.js., MongoDB and React - it’s extremely easy to scale your app and add new amazing functions. It’s time to move on to execution. In sprints.
Our build sprints follow the principles of Scrum - design and development are intertwined in a loop of protyping, testing and improving. We aim high and we do our reality check frequently.
Our team works to build the next set of features according to the product roadmap. In every sprint we put the level of sophistication up and add new functions.
We might sprint to your MVP but we don’t leave quality behind! The designers, developers and product owners continously review the tasks as they’re completed to make sure we only deliver the highest quality code.
We never forget who we’re making these apps for. User testing is integrated in the product development lifecycle and we frequently go back to the customers to test their reactions and make sure we build products that resonate with the target group.
At the end of the sprint, the team discusses their progress and draw conclusions from the tests performed during the sprint. We keep you in the loop and we’re happy to hear your feedback on the features we deliver in each iteration.