Test Operating Model 2.0
Organizations are being forced to be more agile – without speed, they are unable to compete in today’s market place. Therefore, they are putting more focus at the enterprise level to become agile – both in developing the software and in the manner in which they deploy it. However, they are doing so using “legacy” models for testing. Many organizations moved to centralized testing models. Some setup monolithic T-CoEs. While these generated many benefits, they are typically not adaptable enough to support the truly agile organizations. In the same breath, testing only within the agile pods / sprints is also not enough.
Test operating model 2.0
Thus a new model for testing across the enterprise needs to be considered. Not only one, that supports the speed of agile (but also recognizes that many enterprise applications cross the boundaries of their agile teams), but also leverages common services that can be shared across agile teams & non-agile teams. AND, also provides a layer of governance to ensure an optimized level of standard processes, tool usage and reporting.
What constitutes test operating model 2.0?
The Test Operating Model 2.0 typically constitutes of three layers that can be applied to almost any SDLC model. Varying from organizations who are fully waterfall to iterative, to hybrid, to organizations in the midst of transition to agile or even fully agile. The new operating model increases both, emphasis on testing the functionality and test coverage of the product/application. It constitutes of three layers, a project testing team that focusses on testing functions at the pod/sprint level, the LOB (Line of Business) testing team that focusses on cross-functional / End-to-end (E2E) and non-functional testing aspects, thereby increasing test coverage and the enterprise testing team that focusses on re-usability, depicted in the picture below:
The figure below describes how the people, delivery and process of testing changes across the various layers of the new operating model.
Benefit realization of the test operating model 2.0 and progress of implementation, can be accessed by gathering metrics at each layer. The Test Operating Model 2.0 though can be applied to all kinds of organizations, but have great benefits when applied to medium or large organizations which have scale and multiple testing teams.
Why should organizations adapt to the new test operating model 2.0?
Through this model, organizations can leverage synergies of scale, increase visibility, standardize, become more efficient & agile and improve governance leading to expedited savings, increased flexibility, continuous improvement and overall higher quality. The time taken for organizations to transform into this model with a detailed business case and custom solution, achieve cost benefits and improved quality may vary from 3 months to even a year. This will be, based on the organization’s current maturity, size, people skills and leadership mandate.
How to get started?
Mindtree can engage with potential customers in varied forms of test advisory services, ranging from dipstick analysis to enterprise test consulting and guide organizations to re-design the ways of working for testing teams. At Mindtree, we have taken various kinds of organizations (including medium & large) through a phased transformation journey from Siloed testing model to the new Test Operating Model 2.0. This has enabled organizations to reap the benefits in the range of 20% to 40% cost & effort savings.