Unlocking Flow Efficiency in SAFe: A Friendly Guide to Thriving in Agility

Autor: Javier Morillo Oteo

Imagine you’re the chef in a bustling kitchen, preparing a signature dish for a hungry customer. Your team chops, cooks, and plates, but sometimes ingredients arrive late, someone’s left waiting, or a dish needs redoing because it wasn’t perfect.

The result? The customer waits longer than necessary, and everyone’s a bit stressed.

In the world of enterprise agility, the SAFe® (Scaled Agile Framework) is like that kitchen, and flow efficiency is the key to delivering dishes (or value) quickly and with quality.

In this article, we’ll simplify what flow efficiency is in SAFe, how to calculate it, what affects it, and how to improve it, using our agile kitchen as an example. Whether you’re a Release Train Engineer, Scrum Master, Product Owner, or just curious about scaled agility, this guide is for you!

What is Flow Efficiency?

In our kitchen, flow efficiency measures how much time we spend actually cooking (creating value) versus the total time the customer waits for their dish. In SAFe, it’s the same: the percentage of total delivery time spent working on something valuable for the customer, without waits or waste.

Key Concepts with a Kitchen Twist

• Value Demand vs. Failure Demand: Value demand is when the customer orders a delicious pasta dish. Failure demand is when the dish comes back because it was cold or poorly cooked. In SAFe, we focus on getting it right the first time to avoid “returns.”
• Lead Time: The time from when the customer orders their dish to when it’s served. This includes everything: waiting for ingredients, cooking, plating, and any delays.
• Touch Time: The actual time spent chopping, cooking, or plating the dish. That’s what adds value!
• Cycle Time: The sum of all touch times (e.g., chopping + cooking + plating).
• Waste and Wait Time: Waste is anything that doesn’t help the dish, like waiting for tomatoes or cleaning up an unnecessary mess. In SAFe, tools like Value Stream Mapping help identify this waste.
• Blockers: Imagine you can’t cook because the right pan is missing. In SAFe, cross-functional teams resolve these blockers during PI (Planning Interval) planning.
• Multitasking: If the chef tries to cook three dishes at once, everything slows down due to constant task-switching. In SAFe, we limit Work in Progress (WIP) to stay focused.

In unoptimized kitchens (or SAFe systems), flow efficiency can be as low as 10%. That means 90% of the time is lost to waiting or errors!

How to Calculate Flow Efficiency

The formula is straightforward:

Flow Efficiency (FE) = (Cycle Time / Lead Time) × 100

Back to the kitchen. Let’s say we’re preparing a pasta dish:

• Chopping ingredients: 1 hour (value-added).
• Cooking pasta: 2 hours (value-added).
• Preparing sauce: 1 hour (value-added).
• Plating: 0.5 hours (value-added).
• Wait time (missing ingredients, kitchen queues, etc.): 20 hours.

Cycle Time = 1 + 2 + 1 + 0.5 = 4.5 hours
Lead Time = 4.5 + 20 = 24.5 hours
FE = (4.5 / 24.5) × 100 ≈ 18.4%

Only 18.4% of the time was spent cooking! In SAFe, tools like Kanban boards or flow metrics help calculate this automatically and pinpoint areas for improvement.

Visualizing Flow Efficiency

Picture a chart showing how your dish preparation flows over time. In SAFe, we use tools like the Cumulative Flow Diagram (CFD) or value stream maps to spot where work gets stuck. For example:

• End-to-End Efficiency: Measures from when the customer orders the pasta to when they eat it (including backlog waits).
• Team Efficiency: Only the time the team controls (excluding external delays, like late ingredient deliveries).

If efficiency drops, check for excessive waiting or team overload. In our kitchen, maybe the chef waits too long because suppliers are late.

What Slows Down Flow in Our Kitchen?

Here are the main “thieves” of efficiency in SAFe, applied to our kitchen:

1. Poorly Designed Processes: If the kitchen flow (from pantry to plate) is chaotic, unnecessary waits occur. Use Value Stream Mapping to streamline it.
2. Dependencies and Blockers: If the chef can’t cook without tomatoes, everything stops. In SAFe, map dependencies during PI Planning.
3. Multitasking: If the chef juggles pasta, soup, and dessert, everything slows down. Limit WIP with Kanban boards.
4. Bottlenecks: If there’s one oven for ten dishes, a queue forms. Balance team capacities.
5. Insufficient Capacity: If there are too many orders for too few cooks, the backlog grows. Prioritize key dishes.
6. Poor Coordination: If the chef and assistant don’t communicate, errors happen. Use Daily Stand-ups to sync.
7. Low Quality: If the pasta is undercooked, it needs redoing, which delays everything.

Strategies for a Flowing Kitchen (and ART)

Here are practical tips to make your agile kitchen (or Agile Release Train) run like clockwork:

1. Optimize Processes: Use Value Stream Mapping to spot time sinks (like waiting for tomatoes) and redesign the flow.
2. Resolve Blockers: Identify dependencies (like missing ingredients) during planning and have a backup plan.
3. Reduce Multitasking: Limit dishes in preparation (WIP) and prioritize key orders.
4. Balance the Kitchen: If the oven is a bottleneck, reassign tasks or add capacity (like cross-training).
5. Improve Coordination: Use daily meetings to keep everyone in the kitchen aligned. Plan collaboratively to avoid surprises.
6. Focus on Quality: Define a “perfect dish” (Definition of Done), test early, and learn from mistakes in retrospectives.

Conclusion: Make Your Kitchen Shine!

Flow efficiency in SAFe is like running an agile kitchen that delivers delicious dishes on time. By focusing on value-adding time (cooking) and eliminating waste (waits, errors), your team can deliver faster and delight customers. Start by mapping your flow, calculating your current efficiency, and trying one or two ideas from this guide. Soon, your ART will be serving value like a five-star kitchen!