A Solution Train is necessary when dependencies between multiple trains need to be coordinated. Our Solution Train implementations show that the need to align requirements among the Agile Release Trains (ARTs) should not be underestimated. But how is this alignment and the exact assignment of requirements managed in practice?
To coordinate these efforts, we use a Solution Board, which can look very different depending on the organization. It is at the heart of our solution trains and the central artifact for managing complexity. But where does the information come from which we need to ensure coordination and alignment?
We work with Solution Areas that have proven to be an important layer in highly complex environments. Solution Areas are clusters of highly dependent teams that exist within or between ARTs. They coordinate themselves via Solution Area Boards, which ensure a high level of transparency and alignment within these clusters. These Solution Area Boards are fundamental to the Solution Board.
Working with Large Solution for some years now, we know that Solution Areas, Solution Area Boards, and Solution Boards have proven to be indispensable for aligning several release trains within a Solution Train.