Blog

The issue of the flat backlog

In software, building the thing right is easy… identifying the right thing to build isn’t!

“The issue of the flat backlog”, by Erik Poels

Anyone who has ever worked with software knows how complex these integral systems can get. To keep track of all the changes and to make sure inter-dependencies are still intact after releasing an update is hard, even with a fairly small application. We write down the work that needs to be done in a so-called user story. This format helps to perform a task and clarifies the context of what we need to accomplish.

Starting off with the first few user stories is usually easy and the whole team knows what the expected functionalities are within the newly designed system. It gets more difficult when the amount of user stories starts to grow and everybody involved slowly loses track of the complete system. This is also called the issue of the “flat” backlog. Even when the product owner still has this vision of the final product, it’s hard to communicate where everything fits within the system. Luckily there is a way around it. Jeff Patton even wrote a book about it called ‘User Story Mapping’. This is a pattern that describes the way user stories are organized in a big matrix. It contains the complete picture so everyone has a complete overview and all the tasks are ordered from left to right. (Read this book, it will really help you understand how user story mapping makes growing your product a lot easier for your team).

Flat Backlog vs. story map

User Story Mapping solves a few major issues relating to the traditional use of a backlog:

  • Communications can be visualized on the map.
  • Easily determine which parts of the system have the highest value.
  • Slice out a release strategy to deliver quickly to customers.
  • Create a place to visualize ideas and future possibilities, without losing track.
  • Merge and split user stories based on priority and the effort needed to complete them.
  • Prioritize split user stories so they contribute to the outcome of a functionality or sprint.
  • Find mistakes in the design that couldn’t have been uncovered without the right discussion.

Ideally, a User Story Map is created before the actual production starts and helps to convert the vision and the goal of the project towards individual tasks for the different users of the system. After defining this high-level overview of the system, it’s time to bring in the experts and stakeholders. Bringing in all those people will feel as a big investment and you want to make sure this is the right thing to do. The most important thing you will accomplish by doing this is getting everybody involved in the production, with valuable input, fresh ideas and sometimes even major changes that will benefit the system.

After the creation of the User Story Map the scrum team focuses on the parts that need to be built in the next few weeks. During these ‘sprints’ they discuss in detail every solution that will fit the user story, so they pick the most effective and satisfying one to finish the job. This collaboration between the product owner and the scrum team will enhance the quality of the final product.

Mandatory Literature

User story mapping is a valuable tool in software development. This insightful book examines how this often-misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features. Author Jeff Patton shows you how changeable story maps enable your team to have more clear communication about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why.

We are software “architects, analysts, techies and designers” and throughout the years we’ve created a pragmatic and creative approach to identify the right problems to solve before you start with the development of the bits and bites. No long research studies, no thick reports but 4 clear steps to success.

Are you solving the right problems, or are you making software that nobody asked for?

Get in touch, we’d love to hear from you.

Follow us on LinkedIn for more news!

Other news

blog

Automatiseren van bedrijfsprocessen. Zo doe je dat!

Weten hoe je bedrijfsprocessen het beste automatiseert? Ontdek hoe bedrijven door automatiseren van deze processen stukken efficiënter zijn.

blog

Legacy software migreren

Welke strategische overwegingen maak je en hoe kies je het juiste moment?

Event

Mendix Meesterwerk = VOL

Mendix Meesterwerk, een hands-on workshop om zelf te ervaren hoe low-code app development kan helpen met het tackelen van jouw uitdagingen.

news

Bizzomate start samenwerking met MKB Limburg

Deze strategische samenwerking biedt Limburgse MKB-bedrijven directe toegang tot Bizzomate's digitale expertise.

blog

The road to becoming a Mendix MVP

Colleague Coen Spinhoven was recently named Mendix MVP, check his story in becoming a Mendix MVP

blog

De 3 grootste uitdagingen van de structure-fase, en hoe pak je ze aan

Het werken met low-code biedt veel voordelen, maar is geen magische formule voor succes. Wat zijn deze uitdagingen en hoe los je ze op?

blog

DevTools for better security and performance

Free to use Bizzomate DevTool gives Mendix developers more insight in application status, security and performance

blog

Werken met gelukkige en energieke collega’s? Dit doen we bij Bizzomate aan vitaliteit

Om goede prestaties te leveren en ervoor te zorgen dat je lekker in je vel zit is het belangrijk dat iemand zich ook goed voelt.

news

Persbericht Bizzo Meet & Mx: ‘Taking low-code to the next level’

Om low-code naar een hoger niveau te tillen in je organisatie is naast een visie ook een gezonde dosis lef nodig

blog

Hoe behoud je momentum in de structure-fase?

Het momentum vasthouden in de structure-fase is cruciaal. Hoe pak je dat aan en welke middelen kun je inzetten om dat te bereiken?

blog

Automatiseren van bedrijfsprocessen. Zo doe je dat!

Weten hoe je bedrijfsprocessen het beste automatiseert? Ontdek hoe bedrijven door automatiseren van deze processen stukken efficiënter zijn.

blog

Legacy software migreren

Welke strategische overwegingen maak je en hoe kies je het juiste moment?

Event

Mendix Meesterwerk = VOL

Mendix Meesterwerk, een hands-on workshop om zelf te ervaren hoe low-code app development kan helpen met het tackelen van jouw uitdagingen.

news

Bizzomate start samenwerking met MKB Limburg

Deze strategische samenwerking biedt Limburgse MKB-bedrijven directe toegang tot Bizzomate's digitale expertise.

blog

The road to becoming a Mendix MVP

Colleague Coen Spinhoven was recently named Mendix MVP, check his story in becoming a Mendix MVP

blog

De 3 grootste uitdagingen van de structure-fase, en hoe pak je ze aan

Het werken met low-code biedt veel voordelen, maar is geen magische formule voor succes. Wat zijn deze uitdagingen en hoe los je ze op?

blog

DevTools for better security and performance

Free to use Bizzomate DevTool gives Mendix developers more insight in application status, security and performance

blog

Werken met gelukkige en energieke collega’s? Dit doen we bij Bizzomate aan vitaliteit

Om goede prestaties te leveren en ervoor te zorgen dat je lekker in je vel zit is het belangrijk dat iemand zich ook goed voelt.

news

Persbericht Bizzo Meet & Mx: ‘Taking low-code to the next level’

Om low-code naar een hoger niveau te tillen in je organisatie is naast een visie ook een gezonde dosis lef nodig

blog

Hoe behoud je momentum in de structure-fase?

Het momentum vasthouden in de structure-fase is cruciaal. Hoe pak je dat aan en welke middelen kun je inzetten om dat te bereiken?