Presentation to IDBI Fortis

Malaysia New Jersey Mumbai Chennai Bangalore Dubai London Saudi Arabia Malaysia New Jersey Mumbai Chennai Bangalore Dubai London

Mumbai, 27 May 2010

MAVERIC SYSTEMS CONFIDENTIAL

Maveric’s concept of Test Factory
Decentralized Testing
• Distributed testing teams
• Ad hoc/unplanned testing requirements
• Variations in rigor and process of testing
• Sub-optimal talent usage
• Tool investments and infrastructure not optimized
• Automation of testing get lesser focus
• Better collaboration between developers & testers
Managed Test Services
• Centralized talent pool
• Standardized processes
• Better re-use through central repository
• Quality driven by tight metrics management
• Clear focus on performance & test automation
• Sharing the environments
• Better ROI on testing investment
Roadmap for IDBI Fortis – SIT Manual Testing to Test Factory
Level 1 – Initial
• System Integration Testing
process setup
• Implement & customize the test
management tool
• Devise Test strategy for major
releases planned
• Test design naming standards
• Establish the approach to derive
test scenarios and test cases
• Test Design review process setup
• Establish mechanism to identify
the test coverage and traceability
assessment
• Setup and automate defect life-
cycle in the test management tool
• Establish requirements based
reporting, test design reporting,
test coverage reports & execution
results and defect reports
Level 2 – Intermediate
• Test organization setup for
Test factory
• Identify the functions/modules
for automation
• Implement & customize the
test automation tool
• Design and Execute the
automation scripts
• Integrate the test automation
tool with test management tool
Level 3 – Matured
• Establish test repository
through test management tool
• Organize test assets in the test
management tool for quick
reuse
• Reuse the test assets for any
new product launch
• Automation to focus on
business led automation and
adaptability to change
• Automated regression test
pack creation
• Conduct impact based testing
on any new changes
introduced
Test Factory

Test factory is a centralized testing team that will serve

What is Test
specific, named or all software applications pertaining to
Factory?
particular business unit
It ensures that all the risk factors of the testing processes
With our What does it
are detected and managed and that the stakeholders are
experience in do?
notified while testing and measuring the metrics
Elixir, we can
crash timelines It will be setup with mix of Maveric test team and business
How is it
to build up test users from the customer to strengthen the testing factory on
setup?
repository for domain and as well on testing
Core Life Testing factory will have dedicated testing team and they
What does it
Admin operate using the best practices, processes and
comprise of?
application methodologies
(Elixir) It guarantees that the business critical functionalities are
validated properly at the right time
What are its
benefits? This approach will give more flexibility and sharing of
knowledge and experience between the test team and
business users and reduce the dependency in the long term
Key benefits to Testing Factory
Immediate to near term benefits Long term benefits

Lower cycle time for testing Knowledge repository

• Systematic automation • Library of artifacts
• Faster testing through better productivity • Common frameworks
• More re-use • Template and data repositories
• Process for faster speed-to-market • Dedicated competency center

Better application quality through testing
• Rigorous processes
• Better coverage through better design\
• Early identification of defects
• Consistent methodologies
Better quality “First time right”
• Testing will travel upstream in SDLC
• More control on application reliability
• More control on development vendor/teams
• Continuous test process improvement

Better ROI on testing investment Ongoing YoY reduction in testing cost

• Centralized testing • Better retention of testing talent
• Optimization of tools and infrastructure • Better utilization of testing tools
• Better quality testing talent • Investment in partner will pay-off
• Increase in remote/offshore testing
Tangible benefits, both in the near and long
term will ensure sound return on testing
investment
Maveric approach to setting up a Test Factory (1/2)
TIME and MATERIAL BASED MODEL
Planning Phase: Pilot Phase: Scale-up: Steady State:
Roadmap building Demonstrate Delivery Focus on Productivity, Focus on Process
Excellence Cycle time & Invest- Maturity & Org
ment optimization building
12 days 12 weeks 12 months Ongoing
• Prioritize application • Deliver quick wins to • Highly flexible • Strong metrics based
areas for pilot demonstrate tangible resourcing model with project governance
• Put in place road map improvement core and flexi teams • Y-o-Y cost reduction in
and deliverables for 0- • Take mix of functional • Strong offshore delivery testing through better
6 months, 6-12 months and non-functional tests • Systematic test process productivity and lower
and 12-18 months • Demonstrate Maveric’s implementation and cycle times
• Quick mapping of test process, test audit across projects • Move towards fixed
applications and governance process • Clear go-no-go for pricing and test case
release plans for next • Establish clear entry shipping apps out of based pricing
12 months and exit criteria in dev shop • Industry best practices in
• Present objectives for testing • Better use of tools testing leading to early
pilot phase • Put together business across projects for defect identification and
case and test strategy better productivity hence lower cost of
for scale up phase quality

Accountability for End-to-End functional and non-

functional testing
Maveric approach to setting up a Test Factory (2/2)

Phases Deliverables Verification Validation

Test Initiation • Test planning • Verification by Test Manager • Sign off by Business Users
and Planning Document for Milestones and Timelines and Approving authorities

Design • High level Test • Verification against BRD, FS, • Client review and sign off of
• Scenario Test User Manual all the deliverables

• Conditions Test • Preparation of high level • Direct interaction with

Cases/Steps scenarios business users

• Traceability • TL reviews all the documents

Matrix • BA reviews critical
functionalities
• Random Review by IDBI
Fortis Test Manager

Execution • Test Defect • Verification by TL on Defects • Discussion of Logged

Reports Identified Defects in Defect Closure
meeting with Application
development team

Close out • Final Test Report • Review of Test Closure report • Sign off by business users
by BA / TM
Thank you!!!