Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Defining the correct scope of testing transformation

Posted on: 22 August '13

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:

Software Testing Process

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.