Relationship between Development Value Stream and an Epic in SAFe

In the Scaled Agile Framework (SAFe), the relationship between a Development Value Stream and an Epic is as follows:

Development Value Stream

• A Development Value Stream consists of the people, processes, and technologies used to build and deliver the solutions that enable Business Value Streams.
• It encompasses the work of Agile Release Trains (ARTs) and teams that deliver system features, enablers, and capabilities.
• Its focus is on producing solutions that support the outcomes of the Business Value Streams.

Epic

• An Epic is a large, cross-cutting initiative or capability that provides significant business or customer value. It often requires coordination across multiple ARTs or teams within the Development Value Stream.
• Epics are usually broken down into smaller pieces, such as Features and Stories, to facilitate incremental delivery.

Relationship Between Development Value Streams and Epics

1. Epics Are Realized Within Development Value Streams:
   • Epics are often initiated to achieve strategic objectives or to enhance the effectiveness of the Business Value Streams.
   • They require work across one or more Development Value Streams to deliver the desired outcomes.
2. Epics Drive Work in Development Value Streams:
   • The implementation of an Epic typically involves defining Features, Enablers, and Stories that are executed by Agile teams within the Development Value Stream.
3. Epics Align with Value Stream Outcomes:
   • Epics are prioritized based on their contribution to business outcomes, ensuring that the work of the Development Value Streams remains aligned with the overall business objectives.
4. Portfolio Kanban Facilitates Flow:
   • The Portfolio Kanban system helps manage Epics, ensuring they align with the capacity and focus of the Development Value Streams. This ensures smooth flow and delivery of Epics in a way that maximizes value.

Example:

Epic: Enable Dynamic Pricing for Bike Servicing

• Business Value Stream Impact: Increases revenue by optimizing pricing based on service demand.
• Development Value Streams Involved:
  1. Customer Booking System Development: Add support for displaying dynamic pricing in the app.
  2. Payment System Development: Ensure dynamic prices are reflected correctly during payment processing.
  3. Analytics Development: Build tools to calculate demand-based pricing.

The Epic represents the strategic initiative, while the Development Value Streams provide the execution structure to deliver it incrementally and iteratively.

Let’s explore Epic breakdowns and Value Stream coordination in SAFe in more detail, focusing on how Epics are defined, managed, and executed within Development Value Streams.

1. Epic Breakdown in SAFe

Epics are large initiatives that require decomposition to facilitate delivery. Here’s how the breakdown process works:

Step 1: Capture the Epic in the Portfolio Backlog

• An Epic starts with an idea to deliver significant value.
• Captured in the Portfolio Backlog with a concise Epic hypothesis statement, which includes:
  • Business Outcome: The intended value of the Epic.
  • Lean Business Case: An analysis of benefits, costs, risks, and alignment with strategy.
  • Key Metrics: Measures for success.

Step 2: Analyze the Epic

• The Epic is analyzed in the Portfolio Kanban, which helps determine:
  • Feasibility.
  • Alignment with strategic themes.
  • Prioritization based on WSJF (Weighted Shortest Job First).

Step 3: Split Into Features

• Once approved, the Epic is decomposed into smaller Features. Features are deliverable increments of value that are:
  • Small enough to be implemented within a Program Increment (PI).
  • Prioritized in the Program Backlog.

Step 4: Features Drive User Stories

• Features are further broken down into User Stories at the team level.
• Stories are completed in iterations, contributing incrementally to the Epic’s goal.

Example of Breakdown:

• Epic: Enable Dynamic Pricing for Bike Servicing
  • Feature 1: Develop dynamic pricing algorithms.
  • Feature 2: Update UI/UX for pricing visibility in the booking app.
  • Feature 3: Integrate dynamic pricing into payment workflows.
  • User Stories for Feature 1:
    • Write a formula for demand-based price calculation.
    • Validate pricing based on historical data.
    • Deploy pricing API to the booking platform.

2. Value Stream Coordination in SAFe

Coordination ensures multiple teams and ARTs within a Development Value Stream can align their efforts effectively for Epic delivery.

Key Roles in Coordination:

• Epic Owners:
  • Responsible for shepherding the Epic through its lifecycle.
  • Work with Agile Release Trains to ensure Features and Stories align with the Epic’s objectives.
• Release Train Engineers (RTEs):
  • Facilitate alignment between teams within the ART.
• System Architects/Engineers:
  • Define technical solutions and enablers that support the Epic.

Mechanisms for Coordination:

1. Portfolio Kanban:
   • Ensures the right Epics are prioritized and ready for execution.
   • Aligns Epics with strategic themes and Business Value Streams.
2. PI Planning:
   • During PI Planning, teams from across ARTs and Value Streams coordinate to break down Features and plan their implementation.
   • Ensures dependencies are identified and managed.
3. Solution Train Coordination (if applicable):
   • For very large initiatives spanning multiple ARTs, Solution Trains provide additional coordination and governance.
4. Sync Meetings:
   • Regular meetings like Scrum of Scrums and Product Owner (PO) Sync ensure continuous alignment across teams working on the Epic.

3. Delivering the Epic Incrementally

SAFe emphasizes delivering value incrementally. Each increment (Feature or Story) contributes to the Epic’s overall goal. This allows:

• Faster feedback loops.
• Early delivery of partial value (e.g., dynamic pricing for one service type before scaling).
• Risk reduction through iterative delivery.

Example of Incremental Delivery for Dynamic Pricing Epic:

• PI 1:
  • Deliver backend algorithms for dynamic pricing.
  • Implement pricing API and test with limited services.
• PI 2:
  • Roll out dynamic pricing to all services in the app.
  • Integrate dynamic pricing into the payment flow.
• PI 3:
  • Analyze feedback and optimize pricing algorithms.

Summary of Key Points:

1. Epics are broken down into Features and Stories to make them manageable.
2. Development Value Streams coordinate to deliver Epics incrementally.
3. Coordination mechanisms like Portfolio Kanban, PI Planning, and Sync Meetings ensure alignment.
4. Continuous feedback is leveraged to adapt and refine the delivery of Epics.