At ahead we spend a lot of time improving our process of building our product. We follow a Kanban-influenced approach. We ditched Scrum because there were a lot of time-consuming processes involved that didn’t serve us.
I’d like to share a snapshot of how we build our product. You may find this benefitial if the traditional To-Do, Doing and Done seems too limiting for you and you require more detailed stages.
The following stages Idea and Research & Validate are handled with ProdPad. This is also where all our customer feedback comes together.
Two questions have to be answered to be allowed into the idea box.
The assumed value is also the hypothesis to test. Problems should be backed up by some kind of feedback patterns emerging. Problems are not solution proposals like “I need a bigger navigation button”.
This stage is optional. Sometimes a problem is clearly understood and the “unknowns” about it are limited. In that case, an idea can go to Start development right away.
Each research method is tailored to the idea it should investigate. If the problem and value aren’t backed up by anything, but we think there might be something to this, we go into further research. Some undertakings remain an experiment and you never know how it will perform until it’s live.
If an idea has successfully gone through these two filtering stages, we create it as a user story in Azure DevOps.
The user story is ready for our development team to invest time into. They’re ordered from top to bottom from highest to lowest priority.
This stage is divided into two parts.
In addition to a clear problem statement and value proposition, the following acceptance criteria about the user story have been answered and agreed upon by the team.
Developers and Designers get together collectively to break a user story down into (technical) tasks. Clarify who will start working on what.
Getting our hands dirty! Firing up the code editors. Pair- or mob-programming works best.
This stage is about getting an outside perspective and assuring quality.
Shipped to customers, well done.
How did you adapt Kanban to your team? What would you improve in our flow? This is always work(flow) in progress and I’d love to hear your feedback. Shoot me a message and let’s discuss.