Multi-Speed Delivery Model

Overview

The SAFe® based Multi-Speed Operating Model helps in selecting relevant delivery methodology as per the need of the business case requirements. Example - If a particular business case has requirements ideal for waterfall ways of delivery against another business case has requirements relevant for agile ways of delivery, then decision can be made prior to implementation readiness stage in selecting relevant delivery methodology as shown below in the framework.

Key considerations

One key consideration in successful adoption of Multi-Speed SAFe®  ITOM, if to design the implementation cadence appropriately. For example - the agile workstream, which is a fast paced frequent methodology, can follow a “Trunk based development” approach, where are the Traditional waterfall methodology can follow a “Branch based development” approach, where code of both workstreams will be integrated on periodic basis based on common working agreements within and between ARTs.

• Support Functions are the shared teams which support ARTs in accomplishing key activities like Solution Demo, Product deployments, Release activities, and governance

• Support tools are the tools stake which can be leveraged by the ARTs and the support functions in accomplishing continuous/frequent delivery concepts

• The Integrated Platform & Tools enabled by DevOps for Continuous Delivery, would support both Agile and Waterfall alike. The code based from both work streams would be integrated together at a common cadence point, and the subsequent QA and deployment would follow.

• Architectural Runway would also support both work streams, creating platform and technology landscape for subsequent functional requirements (BRDs & Epics)