2. What does traditional testing offer?
Discrete, independent
Waterfall Methodology
Requirements Architecture Developm
Testing Release
Gathering & Design ent
Focused on defect identification
1
19. And an organizational transition plan based on
current maturity level
Stakeholder Discussions
Evaluate Industry best practices
Inputs Define
Current QA Inputs
Future State
Artifact Analysis
State Methodology Adopted
Focus on
• Process & Methodology Focus on
• Tools • Risk appetite
• Infrastructure • Cost constraints
• Operating Model Identify • Available time
• People: Skill set/Roles implementat • Priority areas
ion priorities • Current & Future
state gap
Stakeholder Validation Draw
Inputs Implementation
18
External dependencies Roadmap
21. And most importantly, do not forget to
communicate
• Ensure Executive & Stakeholder buy-in on the
change
• Establish a communication channel for regular
updates and feedback
20
22. Summary
• Traditional testing approaches are being replaced by a “shift-
left” approach to accommodate current business realities
• Shift away from GUI based testing to component based testing
• Focus on both QE and QA based testing – prevention rather
than identification: Need for “Smart Testing”
• Automation becomes critical to maintain the ever reducing
testing window
• New facilitators have risen: Community Testing, Service
Virtualization, Test Environment Management
• However, it is very critical that the organization has a well
thought out transition plan to accommodate these changes
21
And, DO NOT forget to communicate!