epic-slicing-planning

To plan an epic roadmap with vertical slices, define Epic-level design boundaries, shared decisions, and cross-cutting constraints first. This produces a dependency-ordered roadmap with milestone intent and an initial vertical-slice backlog ready for detailed planning.

Epic slicing is needed when planning large features spanning multiple milestones and cross-cutting decisions. It applies to initiatives requiring alignment of architecture, scope, and dependencies across teams before detailed implementation tasks begin.

Align stakeholders on architecture decisions by documenting Epic design boundaries, ADR links, and Q-NNN identifiers. Sharing a vertical-slice plan ensures cross-team scope alignment and prevents over-commitment before work starts.

The best way to define epic boundaries and dependencies is establishing an Epic-level architecture with documented constraints and ADR links. This creates clear scope boundaries and a dependency-ordered vertical-slice roadmap for cross-team alignment.

Epic planning is designed specifically for initiatives with cross-cutting architectural decisions. It maps shared decisions, cross-cutting constraints, and dependencies across teams to satisfy requirements for multi-milestone feature rollout.

Planning large features fails without vertical-slice roadmaps due to unclear boundaries, ambiguous dependencies, and late team alignment. Establishing Epic-level design and an initial vertical-slice backlog prevents over-commitment and documents scope before decomposing work.