E2E Testing in Agile – A Necessary Evil Siddharth Prabhudas, Director IT Saurabh Jain, Scrum Master Optum Global Solutions

35% Defects with considerable business impact are identified during E2E Testing

Major Forces @ work in Large Scale Projects

Accelerated Business Demands Maximize Value Responsiveness to change at reduced cost Increase Profitability Early validation of business case Accelerated Business Demands Complex Landscapes Agile Implementation Large Scale Integration

Large Scale Integration Complex Landscape Mixed Methodologies Distributed Teams Lots of Interacting Systems Large Size Multiple Technologies Accelerated Business Demands Complex Landscapes Agile Implementation Large Scale Integration

Large Scale Integration Agile Implementation Shift Left Cross Functional Deploy Fast Agile Work Smart Accelerated Business Demands Complex Landscapes Agile Implementation Large Scale Integration Enables flexible, responsive and agile business environment

Large Scale Integration Major Forces @ work in Large Scale Integrations Accelerated Business Demands Complex Landscapes Agile Implementation Large Scale Integration There are opportunities to optimize and improve our implementation practices to support Large Scale projects in Agile World

Success is the Sum of Small Efforts Testing an Agile Implementation at Scale + + + Single Team Sprinting Well structured Delivery Quality Requirements well defined Minimum dependencies outside team’s sphere of influence Success is the Sum of Small Efforts

E2E Success is not the Sum of Small Efforts Testing an Agile Implementation at Scale: The Challenges Who does what Manage minimum level of Test and Quality E2E Quality Strategy??? Identify dependencies Large Scale – Multiple Teams Sprinting E2E Success is not the Sum of Small Efforts

Testing an Agile Implementation at Scale : The Challenges Component Coverage 95% Team 1 95% Team 2 95% Team 3 95% Team 4 95% x 95% = 90% 90% x 95% = 85% 85% x 95% = 80% End to End Coverage

Dependency on other teams to create a releasable increment Testing an Agile Implementation at Scale: The Challenges Synchronous or Asynchronous Iteration Model Increment Release dependent on the team with lowest velocity Need of a Hardening Sprint/In Sprint Integration Large Scale – Multiple Teams Sprinting Dependency on other teams to create a releasable increment

Quality Role in Agile

Introducing Release Quality Engineer

Release Quality Engineer : Mindset Change Definition of Quality Promote Visibility into Business context Build foundation of E2E mindset

Synchronized and coordinated No clear sense of direction Release Quality Engineer : Onboard Teams to a common Vision Onboard Teams to a common vision Develop Common Platform Look beyond the application and Across Release Cycles Synchronized and coordinated No clear sense of direction

Release Quality Engineer : Feature Based Development Identify systems and system-to-system interfaces Identify high level business transactions Identify technical workflows and dependencies Analyze the data flow across systems Share the big picture with team

Release Quality Engineer : Engineer in Agile Practices Use cases creation with Business and enterprise architects Acceptance Test Driven Development Baseline Test Data Sets Test Case Automation

Release Quality Engineer : Invert Testing Pyramid End to End Test System Test Unit Test E2E Test System Test Unit Test Start early! Virtualization to simulate cross application responses Complex landscapes are decoupled 4x Improvement possible by inverting the testing pyramid

Release Quality Engineer : Focus on Business Outcomes Demonstrate business benefits Business outcomes based Road Mapping and story mapping Increase coverage and efficiency Reporting test execution results by functional use case

Release Quality Engineer : Risk Management Identify Quality risks Identify indicators Plan mitigation Identify response Monitor Quality risks

Release Quality Engineer : A Case Study A leading healthcare organization, anointed Release Quality Engineers to Key Scaled Agile Programs. The RQEs facilitated End to End Quality Mindset and brought various randomly oriented teams to a common vision. This resulted in successful completion of these programs as per the 5 ONs – On Quality, On Budget, On Scope, On Time, On Benefit

Testing an Agile Implementation at Scale : Conclusion End-To-End Testing is a necessity to infuse customer confidence into the product being delivered, but Relying on extensive end-to-end tests late in the game is fundamentally incompatible with agile concept of Continuous Delivery Effective test strategy should focus on the end-to-end business process Release Quality Engineer: Creates a broad quality community Enables the project team to maintain sight of the big picture Leverages agile development practices Finds synergies between technical workflows and business outcomes High Performance Teams meet desired business outcomes when driven by driven by a goal of high quality with “E2E” focus

Author Biography

Thank You!!!