Scaling up with DevOps – Launching a SAFe® Agile Release Train using IBM CLM and UrbanCode tooling solution
Reedy Feggins 120000A43D Visits (33938)
Last month had the opportunity to lead a six-person IBM agile adoption team in starting an Agile Release Train (ART) in support of a larger telecom project (1000+ users) in Mumbai, India; using the newly released version 4.0 of the Scaled Agile Framework (SAFe® 4.0). In this post, I summarize the business drives, QuickStart approach, and some Early Results collected during the Inspect & Adapt session we conducted at the end of the three-week iteration.
Scaled Agile Framework (SAFe)
While I have had the pleasure of leading several large-scale agile adoptions (1000+ organizations) over the past couple years, I found that the new process guidance in SAFe® 4.0 and improved planning support for large complex programs (agile teams of teams of teams).
In addition, the latest addition of the IBM Collaborative Lifecycle Management (CLM) 6.0.1 and UrbanCode Deploy / Release aligned with the SAFe® 4.0 principles and practices to help the Change Agents demonstrate significant benefits to the key stakeholders including enhanced reporting, better collaboration and improved ability to perform impact analyze at all levels as their business needs change due to competition.
Scaled Agile QuickStart using IBM DevOps Tools
The primary drivers for the Scaled Agile QuickStart were the desire of the Line of Business Leaders to create additional value through the introducing new offerings, onboarding customers faster and reduced maintenance cost for existing solution.
We extended the Scaled Agile QuickStart to three weeks to provide us with additional time to assist the customer with
We assisted the teams with decoupling Program Epic from detailed features by introducing an additional backlog which allowed the Product Managers and Business Owners to perform more effectively planning and coordination of testing resources (shared environments, test resources).
We also introduced additional Program level dashboards, using some of the new IBM Jazz Reporting Service (JRS) to improve transparency, risk identification, and impact analysis.
Finally, we adopted several additional DevOps practices such as Continuous Delivery and Shift-Left testing by automating deployments of managed environments and including QA/DevOps planning activities to ensure these teams could collaborate earlier and prioritize their work more effectively.
While the pilot is still underway, we expect to be able to report some early results, such as:
For a complete overview of the SAFe solution support in CLM 6.0.1, please check out the
Finally, if you are interested in trying out the SAFe Program support delivered in RTC V6.0.1, you can do that on jazz