03 PointZERO - Is it a reality in offshoringminisites.qaiglobalservices.com/stc2012/Paper_...

PointZERO PointZERO -- Is it a Is it a reality in offshoring?reality in offshoring?reality in offshoring?reality in offshoring?

October 2012October 2012

Agenda

� Consequences of Delayed Testing

�How is PointZERO® implemented

�Challenges in implementing PointZERO® at offshore and means to overcome

�Case Study

2Copyright © Capgemini 2012. All Rights Reserved

�Case Study

�Summary

Consequences of Delayed Testing

� Failing systems in production cost huge money! The money involved in solving the problem in production is lot more than solving the problem in earlier phases.

� Let’s take an example of Railway reservation system. When the system is down

To tell somebody that he is wrong is called criticism. To do so officially is called testing.


� Let’s take an example of Railway reservation system. When the system is down people cannot book tickets online, people cannot cancel their tickets, and they cannot check the status of their reservations! That is a huge loss in terms of money and goodwill.

� The defects identified at later stages cost more. You can identify defects earlier by making testing a part of SDLC right at the time when BA’s, architects and developers are on boarded on the project.

Defect cost related to the stages

Code$500

Production$14000

COST TO REPAIR DEFECT

Planning AnalysisSystem Design$140

Unit Test

$1000

Source: Cutter Consortium/Forrester/Sogeti

System


DEFECT

Time ,cost and resource effort increase exponentially later in the lifecycle

Integration Test

$2500

SystemTest

$4500

Certification Test$7000

PointZERO® vision, which is made up of structured approach of TMap, TPI and Lean focuses on automating any repetitive tasks as much as possible. And it also emphasizes on start as

early with testing as possible.

How is PointZERO® implemented

�Approximately 30 to 50 percent of SDLC consists of testing. The growth is primarily in three dimensions- QA, off shoring and last but not the least, innovation.

� Innovation helps to provide benefits to the customer like productivity enhancing tools, methodologies and new offerings.


�Customer wants testing service provider to treat them as “valued customer”.

�Going forward, it will be an extremely exciting time for IT and for independent testing services providers in particular. Most IT organizations consider it essential to come out with superior quality products and services but also with optimized cost.

How is PointZERO® implemented continued…..

�Cloud computing has an impact on testing just as other areas of SDLC. Cloud is the newest addition to testing arena and how can testing service provider add value to the customer is a challenge.

� Standardization and optimization of test tools

� Processes, QA environments,

� Ability to leverage the right third-party tool expertise


� Ability to leverage the right third-party tool expertise

� Model Based Testing (MBT)

� Using turnkey test solutions for performance testing

� Benefit from automated regression testing

� Use of third-party for infrastructure testing and above all benefit from frameworks help drive validation into upfront SDLC.

PointZERO® implemented - Big picture

Business case, drivers,

Law, regulations

Production &

Maintenance

Value Assurance


Acceptancetesting

Systemtesting

Functional

design

Technical

design

RequirementsProcesses

UnittestingDevelopment

Simulation

Steps in implementing PointZERO®

� The PointZERO® vision has helped many IT organizations enhance processes for testing and optimize overall cost of quality.

� Following standard steps are followed for successful implementation of PointZERO® vision for testing:

• Assess the current state of business at customer location


• Do the feasibility check for PointZERO® implementation

• Define the process for implementing PointZERO® vision in testing

• Implement the vision and monitor the Result, Risk, Time, Quality and Cost

• Make adjustments to follow the PointZERO® vision

Challenges in implementing PointZERO® at offshore and means to overcome

�Delayed Offshore Involvement

� In Rightshore® kind of engagement, the project usually kicks off at onshore and the offshore team is involved at a later stage of the project. Following measures can be used to overcome the challenge of delayed offshore involvement:

• Sales team, FO and BO higher management should be made aware of the benefits of PointZERO® vision

• Involve offshore right from the inception phase of the project.


• Involve offshore right from the inception phase of the project.

• Present the benefits of earlier involvement of offshore

�Difference of Opinion regarding PointZERO® implementation

� PointZERO® is a new concept and teams at onshore/ offshore need thorough knowledge of the

PointZERO® implementation. Both teams should be on same page and any differences of opinion

regarding PointZERO® implementation should be resolved in advance.

Challenges in implementing PointZERO® at offshore and means to overcome continued.....

�Extensive Organization level test processes

� QA processes can be tailored to follow Lean processes. Some strategies that can be used to avoid waste on test processes at offshore:

• Have Automatically generated reports and metrics

• Have Automatically generated test scripts from models

• Automatically maintain cross references


• Automatically maintain cross references

• Stop writing test scripts

• Writing clear high level 'test ideas' or scenarios

• Cut down report contents to the important points

• View 'test reports' as tools for us so that we can gain value from them

• Talk people through 'diagrams' rather than writing a report

�


� Limitations of tool usage

� When Model Based Testing is not ideal to be used in case of requirements format which is not

compatible to be entered in the model to generate automated test cases, effective test design

technique from TMap® can be leveraged to have optimum number of test cases with better

coverage. The main intention should be to have improved coverage with optimum number of test

cases so as to cut down upon extra efforts for test execution.


�Getting buy in from stakeholders

� As there is cost associated with having testing team in early phases and no tangible value add is seen by the stakeholders in having testing team right from requirements phase in project. Getting confirmation from all the stakeholders for early involvement of testing team is really difficult.

� Especially if the Rightshore® model is in place, and testing team is at offshore, it is all the more difficult for offshore to convince onshore who most of the times is not from testing and the client as well.


� Lack of confidence on testers as contributor to requirements phase

� PointZERO® says that if collaboration between dev team and QA team begins early, we can ensure that 90 percent of the desired software functionality will be available when the business is ready, rather than 50 percent, which is a normal scenario.

� But most of the times dev teams and project management does not have confidence on test teams competencies and they are not sure if testers can actually contribute to improving the quality of test basis.


basis.

Case study for a Netherlands project

The problem

� Test team was not involved right from inception and inputs from test team were not taken for requirements or change analysis. Only the BA team was working on requirement gathering, so the implementation part or testing part was not taken into consideration in requirement analysis. Later on the dev team and test team faced lot of problems as some parts were not implementable and not testable.


faced lot of problems as some parts were not implementable and not testable.

�Problem for testing: there was only a test coordinator at onsite who most of the times worked as a postman, so the problem was not visualized by test coordinator.

Integrated picture of system


Analysis

Results

� The requirements were very fluid and so many versions of requirements came into picture. Some Use cases had 35 versions in the second release. So in 5 releases it could have crossed 100. In every test execution there were arguments on why this requirement was not tested when it is there in the UC. But we had to tell them that the requirement got changed after the test cases were finalized.

Defect retest cycles were many due to a difference of opinion between teams for


�Defect retest cycles were many due to a difference of opinion between teams for which version of UC to be considered.

How could it have been better

�Getting all the stakeholders in one meeting\call for requirements finalization would have helped the dev and test team in deciding the scope for testing.

Summary

• Clients always want improved quality and innovation without hampering budgets. Testing

has to juggle the tasks of providing better quality product with less amount of time and

cost!

• PointZERO® is a vision- aimed at increasing business success by parallel and step-by-

step improvement across the application lifecycle, to shorten time to market, avoid and

reduce cost, eliminate risk, and achieve fit to use quality.


reduce cost, eliminate risk, and achieve fit to use quality.

• In addition, implementation of Risk-based testing (RBT) & Orthogonal Array Techniques

(OAT), Model Based Testing(MBT), early automation, test driven testing can further

enhance the effectiveness and efficiency of this overall PointZERO® vision of testing.

• With reduced cost of testing due to offshoring, together with PointZERO®

implementation, significant benefits of PointZERO® can be observed at offshore.

Thank You….


Thank You….

03 PointZERO - Is it a reality in offshoringminisites.qaiglobalservices.com/stc2012/Paper_...

Documents

Transcript of 03 PointZERO - Is it a reality in offshoringminisites.qaiglobalservices.com/stc2012/Paper_...