Principle of Alignment: There is more value created with overall alignment than with local excellence.
The Solution Train is the organizational construct used to build large and complex Solutions that require the coordination of multiple Agile Release Trains (ARTs), as well as the contributions of Suppliers. It aligns ARTs with a shared business and technology mission using the solution Vision, Backlog, and Roadmap, and an aligned Program Increment (PI)
The Solution Train builds large and complex solutions (often described as ‘system of systems’). These may require hundreds or even thousands of people to develop. Examples include medical devices, automobiles, commercial aircraft, banking systems, and aerospace and defense systems. The Solution Train provides the additional roles, events, and artifacts necessary to coordinate the building of some of the world’s largest and most important systems. Also, a failure of such a system can have unacceptable social or economic consequences, so an additional degree of development rigor is required. Many are subject to industry and regulatory standards, and they must provide objective evidence of their Compliance.
Solution Trains allow businesses to build large and complex solutions, including cyber-physical systems (e.g., embedded systems) in a Lean-Agile manner. By aligning ARTs to a shared mission and coordinating the efforts of ARTs and suppliers, the Solution Train helps manage the inherent risk and variability of large-scale solution development and requires the support of additional SAFe roles, artifacts, and events, as illustrated in Figure 1.
Solution trains, like ARTs, operate on the following set of principles:
- Fixed cadence – All ARTs on the Solution Train depart the station on a known, reliable schedule, as determined by the chosen PI cadence. If a Capability misses a train, it can catch the next one.
- A new solution increment every PI – During the PI, the Solution Train integrates as much of the solution as is economically feasible, and within the constraints of the Iteration timeboxes. At the end of the PI, the Solution Train delivers a fully integrated solution increment. The Solution Demo provides a mechanism for evaluating the working solution, which is an integrated solution increment from all the ARTs.
- Solution – Solution Intent is the repository for storing, managing and communicating the knowledge of current and intended Solution behavior. The Solution Context identifies the environment in which the solution operates.
- Compliance – Compliance describes how to use solution intent to achieve high quality while meeting regulatory and industry requirements using a Lean-Agile approach.
- Suppliers – Often playing a pivotal role in solution development, a supplier’s agility influences the Solution Train’s agility.
- PI timebox – All ARTs on the Solution Train use the same PI duration and iteration start/end dates.
- Uses an Economic Framework – The Economic Framework permits fast, effective decision-making within the scope of Value Stream budgets.
- ARTs power the Solution Train – ARTs build the components of the solution, using Lean-Agile principles and practices.
- Inspect and Adapt – The current state of the solution is demoed and evaluated at the Inspect and Adapt (I&A), an event held at the end of every PI for individual ARTs and the Solution Train. Solution Management then identifies improvement backlog items via a structured, problem-solving workshop.
- Develop on Cadence. Release on Demand – Solution trains use cadence and synchronization (Develop on Cadence) to help manage the inherent variability of research and development. However, releasing is typically decoupled from the development cadence. Solution trains can Release on Demand a solution, or elements of a solution, at any time—subject to requisite governance and release criteria.
- The Solution Kanban and Backlog – The Solution Kanban and Solution Backlog are used to manage the flow of solution Epics and Capabilities.
Agile Release Trains Power the Solution Train
Each ART within a Solution Train contributes to the development of the solution, as shown in Figure 2. All development activities typically occur within each ART and are coordinated by the Solution Train, as described below.
Solution Train Roles
Three primary Solution Train roles help facilitate successful execution:
- Solution Train Engineer (STE) is the servant leader of the train. Their oversight allows the train to run smoothly by identifying and resolving bottlenecks across the entire solution. The STE facilitates the large solution-level events and monitors the solution Kanban and solution health via its Metrics. They also work with Release Train Engineers (RTEs) to coordinate delivery.
- Solution Management represents the customer’s overall needs across ARTs, as well as communicating the portfolio’s Strategic Themes. They collaborate with Product Management to define capabilities and split them into features. Solution Management, the primary content authority for the solution backlog, also contributes to the economic framework that governs ARTs and Agile teams.
- Solution Architect/Engineering collaboratively defines the technology and architecture that connects the solution across ARTs. It works with the ART’s System Architect/Engineering team to help guide their portion of the solution’s design.
Also, the following roles play an essential part in the Solution Train’s success:
- Customers are the ultimate buyers of the solution and are involved at every level of SAFe. They’re part of the value stream and are inseparable from the development process. Customers work closely with Solution and Product Management and other key stakeholders to shape the solution intent, the vision, and the economic framework in which development occurs.
- A System Team is often formed for the Solution Train to address the integration issues across ARTs.
- Shared Services are specialists—data security, information architects, and database administrators (DBAs), for example—that are necessary for the success of a solution but cannot be dedicated to a specific train.
Defining the Solution
Solution behavior and decisions are managed in solution intent, the single source of truth and the container for requirements as they move from variable to fixed. In addition to the vision and roadmap, the development of solution intent in an adaptive manner is supported by three additional practices, as shown in Figure 3 and described below.
- Compliance – Describes how SAFe uses solution intent to achieve high quality and meet regulatory and industry standard requirements using Lean-Agile development
- Model-Based Systems Engineering (MBSE) – Describes how emergent requirements and design can be developed, documented, and maintained in more flexible and accessible models
- Set-Based Design (SBD) – Describes practices that support the preservation of options and the move from variable to fixed requirements over time, while deferring decisions to the last responsible moment
Building Solution Capabilities
Building large and complex solutions is not a trivial matter. They often require additional constructs beyond those of a single ART:
- Solution intent as the repository for intended and actual solution behavior
- Solution context, which describes the way a solution fits in the deployment environment
- Capabilities and enablers, which are needed to realize the vision and roadmap for the value stream, and more importantly, to satisfy the needs of customers
The solution is described as having a set of capabilities. Like features, they represent a higher-level of solution behaviors that typically take multiple ARTs to implement, as shown in Figure 4. Capabilities are sized to fit within a PI.
The solution Kanban is used to manage the flow of work to assure the evaluation and analysis of capabilities before they reach the solution backlog, where they await implementation.
The Kanban system also helps limit Work in Process (WIP) to ensure that all the ARTs are synchronized and have the capacity to deliver value together. Larger initiatives defined as solution epics are broken down into capabilities during analysis state in the Kanban.
Coordinating ARTs and Suppliers
Solution trains coordinate the development of solutions within a PI, and they provide for cadence and synchronization of ARTs and suppliers, including PI Planning meetings and the solution demo. In many cases, large solutions require suppliers who develop components, subsystems, or capabilities for the value stream. These suppliers participate in the Solution Train events.
At the start of each PI, planning takes place for all ARTs at the same time, conducted by the ARTs in individually PI planning meetings. But to gain alignment and create a single plan across all trains, as well as manage dependencies between the trains, Pre- and Post-PI Planning meetings also take place. These events result in summarized solution PI Objectives for communication with stakeholders.
The Solution Train holds a solution demo at the end of each PI (sometimes at the start of the next PI). Here, it presents an integrated solution across all ARTs and suppliers to customers and stakeholders from the portfolio and other value streams. After this demo, an I&A workshop is held to improve the process of the entire value stream.
Lean-Agile suppliers can be treated as another ART, participating in all Solution Train events. However, suppliers working in traditional methodologies work against Milestones, but are still expected to attend pre- and post-PI planning, solution demos, and Solution Train I&A. SAFe enterprises help suppliers improve their processes and become more Lean and Agile, to the economic benefit of both organizations.
Releasing and Release Governance
As we noted above, Solution Trains apply cadence and synchronization to manage development. But Solution Trains can deploy an entire solution, or the elements of a solution, at any time the business and market dictates.
In support of this, each Solution Train must establish—or operate within the governance of—a release management function. Release management has the authority, knowledge, and capacity to foster and approve releases. In many cases, release management includes Solution Train and ART representatives, as well as representatives from marketing, quality, Lean Portfolio Management, IT Service Management, operations, deployment, and distribution. This team typically meets regularly to evaluate content, progress, and quality. They are also actively involved in scope management.
Also, release management may be concerned with other elements of the whole solution, including internationalization, packing and deployment, training requirements, internal and external communications, and ensuring compliance conformance to regulatory and standards requirements.
Learn More Knaster, Richard and Dean Leffingwell. SAFe 4.0 Distilled: Applying the Scaled Agile Framework for Lean Software and Systems Engineering, Addison-Wesley, 2017.
Last update: 18 April 2018