product teams with 15K+ people
default
test automation frameworks
default
months for initial rollout
default
Startup-style agility is key for continued innovation and market leadership, but this isn’t easy when you’re completing the largest technology merger in history. Dell ISG’s Storage division was confident that improving collaboration could help them boost innovation while maximizing efficiency and upholding stringent quality standards.
30+ product teams were building, testing, and delivering applications using different methodologies, terminologies, pipelines, and toolsets. Teams meant different things by terms like performance testing and integration testing, and they were completing them with different tools and approaches selected to meet each team’s unique needs. With more standardization, team members could reuse others’ work and even float from team to team—enabling them to complete projects faster.
Abstraction was key for achieving this without disrupting delivery or homogenizing each team’s unique way of working. They analyzed the elements of success from a high-level philosophical perspective, then crafted an abstract CI/CD/CT architecture that specified what activities to address (source control, requirements management, test management, etc.) without prescribing low-level implementation details on how to complete them. In theory, it’s open to all existing tools and methodologies. But the devil is in the details. How do you make something like reusable, collaborative testing a reality across a division with 20+ test automation frameworks?