Back to Stories

How we develop products at Humblebee

So you need to build a digital product or service? This is how we do it.

Johan Uddståhl

Johan Uddståhl

So you need to build a digital product or service? This is how we do it.

We believe that the most successful products are the ones that reach users early. Therefore we apply a “what’s needed” mindset when taking on early stage product development projects. For us, “what’s needed” is the optimal way of describing our focus on prioritising tasks wisely and delivering the highest possible value in the least time possible. In close collaboration with the client, we work in agile multi-disciplinary teams building MVP:s, POC:s and prototypes.

The Design Sprint

The design sprint is an effective process for answering critical business questions by designing, prototyping, and testing ideas with customers. When a client comes to us with a product idea or need this is where we usually start.

We will, together with the client, set up a multi disciplinary sprint team that during a period of about one week will work closely together to solve problems. The outcome of a design sprint is often a tested and validated prototype that is ready to move into MVP production.

MVP Definition

When the dust from the design sprint has settled it’s time to get practical. Together we need to decide on what features goes into the first version of our shiny new product. We start by breaking down the prototype from the design sprint into smaller pieces of functionality or capabilities.

We also try to map out the architectural needs and decide on what services we need to use. To decide on what functionality needs to be in the MVP version we use tools like the prioritisation matrix to get a good overview of the road ahead.

We align, discuss, iterate and decide until we feel ready to go into production mode.

The Dev Sprint

The dev sprint is the optimal follow up sprint after the MVP definition is set. Without losing momentum we quickly move into MVP development. To make sure we don’t spend time on handoffs, the team involved in the design sprint will have key roles in the dev sprint team.

A Dev Sprint team usually consists of people skilled in UX, Visual design, system architecture and development. Together they will iterate the product until they’ve reached the MVP level decided in the MVP definition.

The work is carried out with an agile and iterative way of working, where close collaboration with the client is the key to success. We will start each sprint (1–2 weeks) with a sprint planning. Then the team will start each day of the sprint with a standup meeting where every team member goes through what they did yesterday, what they will do today and if they are currently blocked by something.

Each sprint ends with a sprint demo where all stakeholders involved in making the product a success will be present. Input and discussions will go into and form the next sprint.

Going to market

Before pressing launch button we usually help our clients setup and define KPI’s to make sure you will be able to measure if the product is a success and/or what changes needs to be made in coming updates.

When KPI’s are set and we’ve reached the goals set up by the MVP definition it’s time for the happiest moments of them all, the launch. Here we will either hand over your new shiny product to your internal team of experts or we take care of the launch for you. However you wish to proceed we want to help you show your new thing to the world!

And remember, a digital product in an MVP state is by definition made to evolve and develop. The fun has just begun.

Reach out to me for all things techie at Humblebee. Let’s go build together!

Contact:
Johan Uddståhl
e. johan.uddstahl@humblebee.se
t. +46 (0)70 917 06 18
w. humblebee.se

Written by

Johan Uddståhl

Technical Director

johan.uddstahl@humblebee.se

More stories