top of page
Search

Features. Bugs. Technical Debt. Repeat.


How this Lean Principle Creates Sustainable Agile Delivery


Many organizations associate Heijunka with manufacturing assembly lines, but its underlying principle, leveling work to create predictable flow and reduce waste caused by uneven demand, aligns remarkably well with Agile delivery.


What is Heijunka?


Heijunka (平準化) is a Lean concept often translated as:

Production Leveling or Workload Leveling

Its purpose is to smooth the flow of work by reducing:

  • Overburden (Muri)

  • Unevenness (Mura)

  • Waste (Muda)


Instead of processing large batches of one type of work followed by large batches of another, work is distributed more evenly over time.


Think of it as:

"Delivering a sustainable flow of value rather than responding to every priority change with chaos."

Why Agile Teams Should Care

Agile frameworks such as Scrum, XP, FDD, Kanban, SAFe, and others are fundamentally concerned with:

  • Sustainable pace

  • Predictable delivery

  • Continuous value delivery

  • Reduced bottlenecks

  • Improved quality


These goals are exactly what Heijunka supports. Without realizing it, many Agile teams suffer from the opposite of Heijunka:

Common Symptoms


Sprint 1:

  • 80% feature development

  • Little testing


Sprint 2:

  • Massive testing effort

  • Numerous defects


Sprint 3:

  • Emergency bug fixes

  • Technical debt cleanup


Sprint 4:

  • New feature rush


The result is:

  • Burnout

  • Unpredictable velocity

  • Defects

  • Missed commitments

  • Frustrated stakeholders


Heijunka seeks to create a smoother, more sustainable pattern.


Heijunka in Scrum

Consider a Scrum team developing a SaaS application.


Without Heijunka

Sprint Backlog:

Work Type

Story Points

New Features

45

Defects

0

Technical Debt

0

Refactoring

0

The team delivers many features.

Then defects emerge.

The next sprint becomes a bug-fixing sprint.

Velocity fluctuates wildly.

Stakeholders lose confidence.


With Heijunka

The Product Owner intentionally levels work.

Sprint Backlog:

Work Type

Story Points

New Features

25

Defects

5

Technical Debt

5

Refactoring

5

Architecture Improvements

5

The team delivers fewer features initially.

However:

  • Quality improves

  • Velocity stabilizes

  • Defects decline

  • Technical debt remains manageable

  • Stakeholder expectations become predictable

This is Heijunka applied to Scrum.


Practical Software Development Example

Imagine a company developing a cloud-based Customer Relationship Management (CRM) platform.


The Product Owner receives requests from:

  • Sales

  • Marketing

  • Customer Support

  • Compliance

  • Security


Without leveling, the team might spend:


Month 1

Building sales features


Month 2

Fixing defects


Month 3

Addressing security findings


Month 4

Supporting compliance requirements


This creates a cycle of constant disruption.


Applying Heijunka

The team creates delivery categories:

  • New Features

  • Defects

  • Security

  • Technical Debt

  • Compliance


For every sprint:

Category

Allocation

Features

60%

Defects

15%

Security

10%

Technical Debt

10%

Compliance

5%

Every sprint contains a balanced mix.


Benefits:

  • Security risks are continuously reduced

  • Technical debt never becomes overwhelming

  • Compliance work remains current

  • Defects are addressed regularly

  • Feature delivery continues


The workflow becomes smooth and predictable. That is Heijunka.


Heijunka and Extreme Programming (XP)


XP encourages:

  • Continuous Integration

  • Test-Driven Development

  • Refactoring

  • Small releases


These practices naturally support Heijunka because they prevent work from accumulating in large batches.


Rather than:

Build → Build → Build → Test

XP encourages:

Build → Test → Refactor → Integrate → Repeat

The work remains balanced.


Heijunka and Feature Driven Development (FDD)


FDD focuses on delivering features in small increments. A common risk is prioritizing only visible customer features.


Heijunka encourages balancing:

  • New features

  • Architectural improvements

  • Quality improvements

  • Defect correction


This creates healthier long-term delivery performance.


Heijunka and Agile Capacity Planning

One of the simplest ways Agile teams can implement Heijunka is through capacity allocation.


For example:

Team Capacity Allocation

  • 60% New Features

  • 15% Technical Debt

  • 10% Defects

  • 10% Innovation

  • 5% Learning and Skill Development


This prevents teams from constantly switching between "feature mode" and "cleanup mode."


The Hidden Benefit: Predictability


Most executives don't care whether a team uses:

  • Scrum

  • XP

  • FDD

  • Kanban

  • SAFe


What they care about is:

  • Predictable delivery

  • Consistent quality

  • Reliable commitments


Heijunka directly contributes to all three.


A team that consistently delivers 20 quality features every sprint is usually more valuable than a team that delivers:

  • 40 features

  • Then 5

  • Then 30

  • Then 10

with varying quality.


Key Takeaway


Many people think of Heijunka as a manufacturing tool. It isn't. It is a flow management principle.

Whether you're building automobiles, developing software, implementing cybersecurity controls, or managing a digital transformation project, the same lesson applies:

Sustainable, balanced flow almost always outperforms bursts of heroic effort followed by recovery.

For Agile teams, Heijunka means intentionally balancing features, defects, technical debt, security, compliance, learning, and innovation so that value is delivered continuously, predictably,

and sustainably.


In that sense, Heijunka may be one of the most underutilized Lean concepts in modern Agile software development.


 
 
 

Comments

bottom of page