Pattern for coordinating multiple FL1 teams working on different parts of the same epic in parallel.
Multiple teams. One epic. Worked on simultaneously.
This pattern describes how to track and coordinate when multiple FL1 teams work on different parts of the same epic in parallel.
The Problem
An epic is large enough that multiple FL1 teams can work on it in parallel. But on the FL2 board, it looks like a single item. Who's working on what? When is it actually done? You need a way to track multiple concurrent workstreams against a single coordination item.
How It Works
Multiple copies of the epic are created — one per FL1 team. On the FL2 board, the original epic gets colored avatars (stickers), one per team. When a team completes its part, its avatar is removed from the FL2 item. Only when all avatars are gone can the epic advance on FL2. This makes the multi-team nature of the work explicit and undeniable.
When to Use It
- An epic is large enough to parallelize across multiple teams
- The parts can be worked on largely independently
- You need to track multi-team coordination on a single coordination item
Related Patterns
- Connecting FL — the base pattern this extends for the parallel case
- Connecting FL Sequential — the alternative when teams cannot work in parallel
- Slicing & Merging — parallel slices need to merge back; this pattern handles the coordination layer
Your play!
Get the cards and maps — all 18 FL2 Flow Patterns plus the new "Identify your Flow" companion map (A3 + A2 in EN, A3 in DE), ready to use in your next FL2 workshop or board design session.