Enterprise Solution Delivery
Updated: Jan 12
“Success today is not about changing strategies more often, but about the ability to execute multiple strategies concurrently”.
One of the important seven competencies of SAFe includes ‘Enterprise Solution Delivery’, which helps in guiding lean and agile practices and principles in the processes. It guides in deployment, operation evolution, and development of the software application, network, or system.
Creating large enterprises may be a complex thing as it requires plenty of effort in building it by bringing together people, systems, and components from various departments and organizations.
Why Enterprise Solution Delivery is required?
Engineers, scientists, and developers are the ones who bring the huge realities of mankind into shape. To accomplish these big dreams they required knowledge, innovation, and experimentation from many different domains. These diverse qualities and skills are achieved by engineers and developers to bring these innovations to life. The abilities also include;
Analysis of requirement
Business capacity definition
Functional allocation and analysis
Design synthesis and system design
Modeling and simulation
Building and testing system and components
Verification and validation
Monitoring, deployment, support, and system update.
As there is an update in purpose and mission over time the technology and capabilities are evolved changing the system continuously.
Enterprise solution delivery consists of nine practices that are grouped within three dimensions.
1. Lean System and Solution Engineer
Continually refined the fixed/variable
It replaces the traditional ‘V’ model with updated continuous and concurrent engineering. This divides the activities into a continuous flow of work as a continuous pipeline but in small batches. It helps in aligning system builders in a shared direction. The knowledge gained from this continuous exploration will provide the team with feedback to maneuver decisions from variable to fixed ones.
Solution Intent Apply multiple planning horizons
To avoid the risks and uncertainty in developing large systems agile uses the backlog, feedbacks, and roadmaps to ensure most value is delivered. It provides multiple planning horizons that simplify realistic planning.
Architect for scale, modularity, reliability, and serviceability
An architectural choice determines the future required cost and efforts for the project. It helps in releasing the system independently, allows continuous value delivery, and reduces total owner expenses.
Continually address compliance concerns
Generally, unacceptable social and economic cost causes the failure of large solutions to avoid it system should have regular regulatory oversight and content various compliance needs. As there is an update in digital time it’s good to change the traditional QMS into lean QMS as it makes acquiescence activities part of a flow.
2. Coordinating Trains and Supplies
Build and assimilate solution components and abilities with ARTs and solution trains.
Systems are always built by people. So in agile ARTs are optimized in small groups as a team of an agile team. Solution Train scale ARTs to a large solution with hundreds of developers and suppliers. This train integrates with the whole solution and supports validation and learning in the early stages.
Apply continuous integration
Continuous integration is a central point of continuous delivery. It checks changes and assumptions across the complete system. Large systems are difficult to integrate because of;
A long lead time item is not available.
Automations hardly end to end.
Physics law restricts some limits.
Integration spans organizational boundaries.
Manage supply chain with systems of system thinking
As suppliers working also affects the supply chain they should be integrated into the trains and participate in related events. The customer and supplier system team should integrate properly for the free and smooth flow of the supply chain. In complex cases of supplier integration, continuous backlog and roadmaps must be aligned.
3. Continually Evolve Live System
Build Continuous Delivery pipeline
In software development and other technologies, the CD pipeline is well established but in the cyber-physical community, it is beginning to emerge. Any delivery pipeline needs to continuously evolve as the system always evolves. This evolution of the delivery pipeline is well fitted with the CD pipeline. It optimizes the process, binds it to time, and also removes defects promptly. Cyber-physical systems should use this CD pipeline for better utilization of new functionality.
Evolve deployed system
Adaption of CD pipeline means a change in the economy due to its investment. Quick economical pipeline means a minimum variable system that evolves early. This results in early learning with less investment and also early revenue.
Agile had defined the way to deliver quickly and update often to reinvent and reinvigorate providing a solution that satisfies the customers, making agile the best approach to success. As someone mentioned “Success today requires the agility and drive to constantly rethink, reinvent, reinvigorate and react”.