One-piece flow is inefficient for software development

The Experiment

  • There will be two teams of same size
  • There will be two backlogs of stories with acceptance criteria; one backlog was broken down to tiny discrete stories, “build a chair”, “build a table” and “build a plant”. Second backlog had larger stories with more scope “build a park scene with chair, table and a plant”. There were many different scenes in there that teams had to create.
  • Each team member was constrained as he/she could only work on structures top, middle or bottom part and not the whole. This constraint reflects skill/specialism in real life.

Team A (large scope stories)

Figure 1, Large story team delivering a park scene

Team B (small scope stories)

Figure 2, Small story team delivering a park scene

Conclusion and Implications




Systems Architect | |

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Build automation with Gradle

7 Python Mistakes You Don’t Want to Make

My First React Native App

Transfer Domain from Network Solution to Google Domains

API Testing Tutorial!!

Write Better Commits With Semantic Commits

Elasticsearch parent child join

Evaluating Website Maintenance Packages: 12 Questions IT Must Ask

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Zan Kavtaskin

Zan Kavtaskin

Systems Architect | |

More from Medium

Part 2 (The Bad): Top 3 good, bad & ugly patterns in modern agile teams

Writing Useful Performance Reviews: Making a raise recommendation

How to be a Better Stakeholder

What does an Engineering Manager ?