Everything must be made as simple as possible. But not simpler.

—Albert Einstein



Large Solution Level

The Large Solution Level contains the roles, artifacts and processes needed to build large and complex solutions. This includes a stronger focus on capturing requirements in Solution Intent, the coordination of multiple Agile Release Trains (ARTs) and Suppliers, and the need to ensure compliance with regulations and standards.

Einstein’s quote reminds us that we should strive to make things as simple as possible, but not simpler than what is needed. Similarly, when building large and complex systems, theoretically, the simplest thing that could possibly work would be a single team. But we know that even teams with more than ten or eleven people are problematic. And a single ‘team’ of hundreds, or even thousands of people, just isn’t feasible. Instead, we need teams-of-teams (Agile Release Train) and teams-of-teams-of-teams (Solution Train). Coordinating these activities requires additional roles, events, and artifacts, which is the purpose of the large solution level.


The Large Solution Level (Figure 1.) is meant for enterprises that face the biggest challenges—building large-scale solutions that are beyond the scope of a single ART to develop. Building these solutions requires additional roles, artifacts, events, and coordination.

Figure 1. Large Solution Level


Below are the highlights of the large solution level:

  • Solution Train – is the key organizational element of the Large Solution level, and aligns the people and the work around a common solution vision, mission, and backlog.
  • Economic Framework – provides financial boundaries for the Solution Train’s decision-making.
  • Solution Intent – is a repository for current and future solution behaviors, which can be used to support verification, validation, and compliance. Solution Intent is also used to extend built-in quality practices with system engineering disciplines, including Set-Based design, Model-Based Systems Engineering (MBSE), Compliance and Agile Architecture.
  • Solution Context – describes how the system will interface and be packaged and deployed in its operating environment.
  • Solution Kanban – manages the flow of capabilities and enablers for the solution.


The large solution-level roles provide governance, and helps coordinate multiple ARTs and suppliers, and provides the necessary governance:

  • Customer – is the ultimate buyer of every solution. An integral part of the Lean-Agile development process and value stream, they have specific responsibilities in SAFe.
  • Solution Architect/Engineer – represents an individual or small team that defines a common technical and architectural vision for the solution under development.
  • Solution Management – has the content authority for the large solution level. They work with customers to understand their needs, create the solution vision and roadmap, define requirements (capabilities and enablers), and guide work through the Solution Kanban.
  • Solution Train Engineer (STE) – is a servant leader and coach who facilitates and guide the work of all ARTs and suppliers.
  • Supplier – is an internal or external organization that develops and delivers components, subsystems, or services, which help Solution Trains deliver solutions to its customers.


The large solution level uses three major activities to help coordinate multiple ARTs and suppliers:

  • Pre- and Post- PI Planning – are used to prepare for, and follow-up after, PI Planning for (ARTs) and suppliers in a Solution Train.
  • Solution Demo – is where the results of all the development efforts from multiple ARTs—along with the contributions from Suppliers—are integrated, evaluated, and made visible to customers and other stakeholders.
  • Inspect & Adapt (I&A) – is a significant event where the current state of the Solution is demonstrated and evaluated. Teams then reflect and identify improvement backlog items via a structured problem-solving workshop.


The following large solution-level artifacts help coordinate multiple ARTs and suppliers:

  • Capabilities – is a higher-level solution behavior that typically spans multiple ARTs. They are sized and split into multiple features so that they can be implemented in a single PI.
  • Solution Epics – these epics are specifically for one solution train.
  • Nonfunctional Requirements (NFRs) – define system attributes such as security, reliability, performance, maintainability, scalability, and usability. These are incorporated in solution intent.
  • Solution Backlog – is the holding area for upcoming capabilities and enablers, each of which can span multiple ARTs, and are intended to advance the solution and build its architectural runway.
  • Solution Kanban – is a method used to visualize and manage the flow of business and enabler capabilities from ideation to analysis, implementation and, release.

Solution Trains Deliver Value

The Solution Train is the organizational vehicle that is used to coordinate the efforts of multiple ARTs and suppliers to deliver the world’s largest and most complex systems. They align and coordinate ARTs and suppliers to collaborate like a single team, but have all the advantages inherent in organizing using small teams and ARTs in order to scale.

Apply Large Solution Elements to Other SAFe Configurations

As we have described, there are a number of unique elements which are pictured at the large solution level. However, any individual element of this level may be applied to the Essential SAFe or Portfolio SAFe configurations. For example, Solution Intent and Compliance might be used by a single ART building a medical device of modest scale. As illustrated in Figure 2, this is part of SAFe’s scalability and configurability.

Figure 2 – Applying large solution level elements to other SAFe configurations

Last update: 24 May, 2017