Capabilities & Enablers

A capability is a higher-level behavior of the solution that typically spans multiple ARTs. It's the Large Solution equivalent of a feature—but bigger.

Feature vs. Capability:

• A feature delivers value within a single ART. One team (or a few teams on the same ART) can implement it.
• A capability delivers value across multiple ARTs. It requires coordinated work across trains.

Example for an autonomous vehicle platform:

• Capability: "Vehicle can navigate a highway interchange safely"
  • ART 1 Feature (Perception): Detect lane markings and merge zones at highway speeds
  • ART 2 Feature (Planning): Generate safe trajectory through interchange
  • ART 3 Feature (Control): Execute lane changes with appropriate acceleration
  • ART 4 Feature (Infrastructure): Map data for interchange types

Capabilities live in the Solution Backlog, managed by Solution Management. During Pre-PI Planning, capabilities are broken down into features that feed into each ART's Program Backlog.

Sizing capabilities: Capabilities should fit within a single PI. If a capability spans multiple PIs, it's really an epic and should be managed at the portfolio level with a Lean Business Case.

Just as teams have enabler stories and ARTs have enabler features, Solution Trains have solution-level enablers.

These address cross-ART technical needs:

Architecture enablers: Shared platforms, APIs, and protocols that multiple ARTs need. Example: a message bus that all ARTs publish to and subscribe from.

Infrastructure enablers: Integration environments, testing infrastructure, deployment pipelines that span ARTs. Example: a system-level integration test environment that combines all ART outputs.

Exploration enablers: Cross-ART proof-of-concepts or trade studies. Example: evaluating two competing approaches to inter-service communication.

Compliance enablers: Regulatory requirements that span the entire solution. Example: GDPR compliance that affects how all ARTs handle personal data.

Managing solution enablers:

Solution enablers compete for capacity just like capabilities. Solution Management prioritizes the solution backlog, balancing capability delivery with enabler investment.

A healthy allocation depends on solution maturity:

• New solution: 40-50% enablers (building the foundation)
• Maturing solution: 20-30% enablers (maintaining runway)
• Stable solution: 10-20% enablers (incremental improvements)

The Solution Kanban manages the flow of capabilities and enablers through the system. It's similar to Portfolio Kanban but operates at the solution level.

Typical columns:

1. Funnel — New capability ideas captured but not yet analyzed
2. Analyzing — Solution Management and Solution Architect evaluate feasibility, define acceptance criteria, and estimate size
3. Backlog — Analyzed and ready for PI Planning, prioritized by WSJF (Weighted Shortest Job First)
4. Implementing — Active in the current PI, decomposed into features across ARTs
5. Validating — Integrated across ARTs and being validated at the solution level
6. Done — Deployed and delivering value

WIP limits apply at each stage. The Solution Kanban typically has lower WIP limits than you'd expect—a Solution Train might only have 3-5 capabilities in implementation at once, because each capability requires coordination across multiple ARTs.

WSJF prioritization: Capabilities are prioritized using Weighted Shortest Job First, which balances cost of delay (user/business value + time criticality + risk reduction) against job size. This ensures the highest-value, shortest-duration work gets done first.