Test Environments – The Tracks for Agile Release Trains
by Niall Crawford
Definition: An Agile Release Train is basically a number of teams (a portfolio) responsible for the regular release of features and business benefits. All the teams are bound by a common set of goals, a program backlog, and a roadmap. ART is central to understanding and implementing a Scaled Agile Framework.
And why not? An Agile Release Train (or Enterprise Release Management) methodology is usually much better than the alternative chaos of different project teams running off in different directions (as “fast” as they can), competing for shared resources (service & systems), misaligning group priorities and ultimately causing collective delivery delays due to mismanaged dependencies & relationships with other teams.
If implemented correctly ART will help IT deliver on the necessary IT business transformations as quickly and safely as possible, and ultimately deliver timely solutions into production and to the end-customers.
Key Benefits of the Agile Release Train
- Increased Collaboration
- Improved Change (Feature) Throughput
- Controlled Velocity
- Cross Team Productivity
- Risk Cognizance / Awareness
- Circumvent Release Failure
- Delivery Streamlining
So, we get started by each team loading up the train carriages with Features & Change.
And we collectively commence out journey towards production.
Then the proverbial “wheels fall off”.
Delays in Development, System Test, Integration, UAT & Staging due to:
- Test environment unreadiness (i.e. engineering team is still building it)
- Test environment contention (i.e. BAU Team currently has it)
- Test environment instability due to too much unplanned change
- Test environment systems are not fit for purpose e.g. wrong scale or version or integrations
And the risk of overspend, for example:
- Need for more systems (infrastructure & licensing) to address contention
- Need for more support (services) to accelerate tasks & remediate
And suddenly our ART suddenly looks like something out of “Thomas the Tank Engine”.
The problem with trains, whether real or agile, is they must follow a rail track and delays & collisions will be inevitable if tracks (or the stations) are inappropriately sized, incorrectly built, mismanaged and not kept clear.
In the case of your Agile Release Trains, imagine the train stations as your lifecycle. The ART will travel through each station (Development, System Test, Integration, UAT & Staging) to allow the necessary on-boarding of fixes (good commuters) & offboarding of defects (bad commuters).
Oiling the Track
In IT, preparing the rail track is analogous to the task of IT & Test Environment Management. A multi-faceted set of discipline – refer to the EMMI (Environment Management Maturity Index) – that ensures appropriate:
- Understanding, Mapping & Modelling of Environments & Systems
- Capturing of Demand & Managing of Contention
- Planning & Coordination of Preparation Activities
- Lean Service Management
- Standardised & Repeatable Operations
e.g. Application Deployment & Configuration Activities, Data Masking etc.
- And Continual Analysis & Reporting for Improvement
Benefits to ART of implementing effective Test Environments Management
After bad requirements management, Test Environments are the number one reason for Project delays. Hardly surprising when you consider that is where Projects (and I guess the Agile Release Trains) spends 95% of their time.
By implementing a proper TEM framework (tracks), you ensure:
- Environments Readiness (systems prepared in advance)
- Environments Suitability (systems fit for purpose)
- Environment Stability (disruption/outage avoidance)
- Release Team Productivity (more time to Develop & Test)
- Release Streamlining (Maglev style) &
- Reduced IT Costs through better project sharing & post release housekeeping
So next time someone mentions the ART, ask them about the readiness of the tracks. As trains don’t go too far without them.
Learn More, or Share Ideas
If you’d like to learn more about Release or Environment Management or perhaps just share your own ideas, then feel free to contact the enov8 team. Enov8 provides a complete platform for addressing organisations “DevOps at Scale” requirements. Providing advanced “out of the box” IT & Test Environment Management, Release Management and Holistic Data Management capabilities.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
09 DECEMBER, 2018 by Sylvia Fronczak DevOps promises greater innovation, speed, and automation—along with a more engaged and motivated team. With this list of benefits, many organizations are working to bring DevOps to their teams. However, with all the companies...
22 OCTOBER, 2018 by Eric Goebelbecker Containers are nothing new. Depending on how you look at it, you can make a case for them being around at least since 1982. But since the introduction of Docker in 2013, they’ve enjoyed a surge of popularity. Why? In just a few...
15 OCTOBER, 2018 by Christian Meléndez Preamble A key part of Enterprise IT Intelligence is understanding you Cloud Resources. And where better to start than using the "elegant" concept of Tagging. A concept used across the various cloud and infrastructure management...
26 SEPTEMBER, 2018 by Niall Crawford World Quality Report 2018-19 The results from the 10th anniversary edition of the World Quality Report are conclusive: 99% of respondents are now using DevOps practices in their organizations. It appears the focus is no longer on...
14 September, 2018 by Sylvia Fronczak Incorporating DevOps into your organization is not a zero-sum game. It is a journey. And like most journeys, it can be measured. When measuring your DevOps journey, you need to show progress as well as setbacks. Additionally, it's...
03 SEPTEMBER, 2018 by Niall Crawford Preamble All too often we see companies embracing agile by breaking up their teams up into tribes and letting them go for it. An approach which has the “early benefits” of appearing like your teams are doing the right-thing...