Defining the correct scope of testing transformation
Traditionally, testing transformation initiatives have focused on the software testing phases of the project, emphasizing the right input criteria, outlining the right collaboration and reporting tools, and establishing a solid change management and sign off criteria.
However, testing transformation must focus on one end goal – delivery quality. That implies that traditional transformation approaches fall short by focusing on testing the software, and not addressing the overall organizational dynamics that must be addressed to meet the goal of delivery quality. Note that I did not use the word “high quality” but quality. That’s because quality goals are achieved by meeting the requirements. The requirements define the thresholds and acceptance criteria. Anything below the threshold is quality not met. Using terms like high quality and low quality tend to soften the edge and reduce the attention that must be given to this problem.
Hence quality must be measured at all stages of the organizational process. The following diagram defines the correct scope of testing transformation:
Hence traditional testing transformation approaches miss the following:
- Ensuring that the CIO portfolio is aligned to the business
- Validating what is being tested as the goal
- Ensuring that other stakeholders are working towards the same goal
- Emphasizing zero defects stakeholder
The simplistic approach of Assess – Define – Implement – Refine leaves open several issues which must be interpreted at run time. The right approach starts with an assessment which defines the maturity by organizational units, application portfolios or business processes, and then defines the complexity of change as well to arrive at a roadmap.
To read more about the principles of testing transformation, please view our whitepaper on Guiding Principles and Dimensions of Testing Transformation.
Steps to testing transformation – Adopting lean through catalog based testing models Digital Transformation Explained – Collaborative, Insightful, Futuristic Benefits of an output based testing model Four Steps to setting up an Output based Testing & pricing model Not thinking….automated!
OSMOSIS 2013 - My Experiences Parallels Summit 2014 - Reflections Digital Relationships With Customers: A Key to the Future of the Store Mobile Testing-Part 2 Getting on top of the internet of things View all
A fresh look at metrics and the marketing funnel (5804) Can You Entrust Your Services Partner With Your Demand Reduction Goals? (4114) Crossing Swords – ARMed Intel (3924) What is Consulting? (2739) What is the difference between Marketing and Sales? (2324) View all
What is the difference between Marketing and Sales? (24) Is change inevitable? – A Scrum Master’s dilemma (22) A Dip in the Chart – An Agile Story (17) An inbuilt mechanism for innovation: organic & ecological (16) Mumbai Dabbawalas (16) View all
Creating Sanity Amidst Test Methodology Madness – Webinar Series Transforming Test Organisation MindTree Vlogs: Role of Independent Testing in the Manufacturing industry A Look Back and A Look Ahead Some Brands Never Get Old View all
Is change inevitable? – A Scrum Master’s dilemma A Dip in the Chart – An Agile Story The Perplexed Scrum Master What’s in it for me? (WIIFM) When you are an expert on something, where do you learn from? View all
Find us on