High-Impact Software Releases With 50% Improvement In Time-To-Market

350-person global delivery team uses Mingle and Go to cut time-to-market with superior collaboration, visibility, and automation.

trainline_logo_0

Staying a step ahead led thetrainline.com to embrace Agile and ThoughtWorks to deliver rapid innovation with high responsiveness. Mingle and Go enabled thetrainline.com to not only maximize Return On Investment (ROI) from Agile, but to optimally scale it, to what has now become one of the largest-known Agile projects with over 350 people worldwide.

Download PDF

“Mingle and Go provided us with essential collaboration mechanisms, critical real-time visibility, and optimal automation capabilities for every aspect of the delivery lifecycle.”

David Jack , CIO

The Challenge

  • The scale of the project, the trainline.com is the UK’s leading travel website with 14+ million transactions.
  • High traffic volumes make it critical for the web application to cost-effectively respond to rapid business changes.
  • Issues were integrating and testing different components, and collating status reports.
  • Release anxiety fuelled by complex integrations, and dependencies in a code base that was being developed by over 350 people in 2 time zones.
  • Builds were time-consuming, broke too often, and were difficult to debug.

How did Mingle and Go help?

  • Within a quarter, Mingle enhanced visibility with customized role-based dashboards, real-time reports, and virtual Story walls.
  • Mingle’s interface enabled the huge distributed team to do the impossible – collaborate effectively and easily.
  • The team created single, fully automated, deployment solution that rand 28 builds in parallel. This drastically reduced the feedback time to just 20 minutes.
  • Go’s scalable cloud architecture enabled robust scaling with optimized infrastructure consolidation, which led to huge cost savings.

The Results

Nothing tells a success story better than numbers:

  • Mingle and Go enabled release of tested functionality every 6 weeks.
  • It increased test coverage by 30%
  • It decreased build feedback time by 77%

Read the full theTrainLine.com Case Study (PDF)