← All DORA Capabilities

Trunk-Based Development

Flow & Delivery
CONTEXTUAL INFLUENCER

Trunk-based development (TBD) is a development approach in which engineers integrate changes into a single shared main branch frequently, keeping branches short-lived and the system continuously releasable. It minimises divergence between code paths, reduces integration risk, and enables fast feedback cycles. TBD is a foundational practice for continuous integration and continuous delivery.

When teams rely on long-lived branches, integration becomes complex, testing is delayed, and releases require stabilisation phases. Changes accumulate, increasing uncertainty and the likelihood of defects. Mature organisations evolve toward frequent integration to trunk, supported by automation, testing, and practices such as feature flags to allow incomplete work to coexist safely. At the highest level, the trunk becomes the central nervous system of delivery, enabling rapid collaboration and continuous flow of value.

Long-Lived Branching
(Isolation first, integration later)

Description

Developers work on separate branches for extended periods, integrating only near release time.


Observable Characteristics

  • Feature branches persist for weeks or months
  • Integration events large and disruptive
  • Significant merge conflicts common
  • Stabilisation phases required before release
  • Main branch may not be deployable
  • Collaboration across branches limited

Outcomes & Risks

  • Elevated integration risk
  • Reduced development velocity overall
  • Difficulty coordinating across teams
  • Increased likelihood of release delays
Shorter Branches with Scheduled Integration
(Improved but still cautious)

Description

Teams attempt to integrate more frequently, but branching remains the primary mechanism for managing work.


Observable Characteristics

  • Branch lifetimes measured in days or weeks
  • Periodic merges into main branch
  • Integration often coordinated events
  • Automated tests run during merges
  • Developers cautious about merging incomplete work
  • Main branch stability variable

Outcomes & Risks

  • Better collaboration than long-lived branching
  • Ongoing integration friction
  • Slower feedback than optimal
  • Limited readiness for continuous delivery
Frequent Integration to Trunk
(Main branch as primary workspace)

Description

Developers integrate changes into the trunk frequently, keeping branches short and ensuring the system remains usable.


Observable Characteristics

  • Branches short-lived, typically hours to a few days
  • Developers merge at least daily
  • Main branch kept in a releasable state
  • Strong automated testing required
  • Feature flags used to hide incomplete functionality
  • Collaboration occurs through shared codebase

Outcomes & Risks

  • Increased development velocity
  • Reduced risk of late surprises
  • Strong foundation for continuous delivery
  • Requires disciplined engineering practices
Optimised Mainline Flow
(Integration performance actively managed)

Description

The health and efficiency of trunk-based development are measured and continuously improved.


Observable Characteristics

  • Metrics tracked for merge frequency, build health, and lead time
  • Fast CI pipelines support rapid integration
  • Automated checks enforce standards
  • Policies prevent broken builds from persisting
  • Integration issues resolved immediately
  • Continuous refinement of practices

Outcomes & Risks

  • Efficient collaboration across teams
  • Reliable readiness for release
  • Improved code quality
  • Investment required in tooling and discipline
Continuous Mainline Development
(Trunk as the delivery backbone)

Description

All development revolves around a continuously stable trunk, enabling seamless collaboration and rapid delivery.


Observable Characteristics

  • Changes integrated multiple times per day
  • Main branch always production-ready
  • Advanced techniques such as feature flags and incremental rollout
  • Minimal reliance on release branches
  • Continuous collaboration through shared codebase
  • Integration friction nearly eliminated

Outcomes & Risks

  • Enables true continuous delivery
  • High organisational agility
  • Reduced coordination overhead
  • Strong resilience to change
Maintain a single shared code line with short-lived branches to enable rapid integration and delivery.