do the right thing - empowering your test teams

© 2011 Forrester Research, Inc. Reproduction Prohibited

Webinar:Do The Right Thing – Empowering Your Test Teams

Twitter: #SBevent

Guest Speaker: Margo Visitacion, Vice President, Forrester Research

Host: Derek Langone, President, SmartBear Software


Agenda

Introductions

Do The Right Thing

- Empowering Your Test Teams

Q+A


FAQ

Questions

– You can submit questions at any time

– Use the “Questions” feature in your GoToWebinar Panel

Twitter: Share the event live using #SBevent

Replay will be available at SmartBear.com


Guest Speaker

Margo Visitacion is Vice President at Forrester Research

serving Application Development & Delivery

professionals. Margo focuses on the areas of project

management, project portfolio management, PMO,

software testing, quality assurance, and Agile test

methodologies. While at the independent research firm

Forrester, she has covered project and program

management, project portfolio management, project-based

organizations, integrated IT management, requirements

management, quality assurance, and testing processes.

© 2011 Forrester Research, Inc. Reproduction Prohibited© 2009 Forrester Research, Inc. Reproduction Prohibited

Do The Right Thing - Empowering Your Test Teams

Margo Visitacion, Vice President

March 1, 2011


Quality is hard – it’s time to step up

Empower your QA team to make a difference

Taking a team approach to build on positive change

Adopt tools to streamline the process

Recommendations

Agenda


Making sure your applications meet high quality levels doesn’t have to be hard


Make the most of your budget: one third of spending goes to application development and maintenance


And you must balance quality across new and existing apps






Recommendations

Agenda


To empower your team, you first must realize that quality must be more than testing grown up

80’s/early 90’s

• Quality Assurance • Engineering focus

• Testing = profession• Process driven

• Tools difficult and complex

• Quality multiphase process

• Testing final phase process

Late 90’s/early 00’s

• Quality control• Over the wall

• Testing = necessary evil

• Tool usability increases, adoption

low• Emphasis shifts to

business focus• Attitude shifts to code,

implement, fix

Late 00’s/10’s + beyond?

• Quality management• Combined focus

• Testing = profession• Pragmatic process

• Great usability increase • Broader tools adoption

• Iterative and collaborative testing


Which team are you?

The empowered testing team• Introduced early in the cycle• Part of the development and design process• Part of the project initiation process• Tests early and often• Is enabled to make the tough call

The powerless testing team• Gets content at the last minute• Has no insight into development process• Has little insight into business stakeholders

needs• Cannot hold up the cycle must squeeze their

tests to fit in a compressed cycle if other team members slip


Empowered teams focus on quality from day one

Business determinesobjectives, sets

requirements

Design and developmentbased upon requirements

Set test planning &Automation strategy

Business stakeholders, BAs & test team set quality and performance requirements for functional and non functional

requirements

Development &testing continues

Continuous build and integrationContinuous testingmanual and automatedStatic and automated performance testing starts

End to end testingUAT

DeploymentPost

Mortem


Taking the first steps

User stories

“Situational realities”

Req

uirem

ents

Risks/opportunities

Drives:

• Test planning

• Automation strategies

• Identification of sourcing needs


Empower your team to set the bar before testing even begins

Requirements

•Quality thresholds

•Performance thresholds

•Performance ranges

•Negotiable and non negotiable

Design

•Determining testability

•Data mapping

•Integration testability

•Mapping automation strategy

Developme

nt

•Functional testing design

•User experience design

•Performance design

•Regression testing design






Recommendations

Agenda


Empowerment doesn’t belong to testers alone

BusinessStakeholders

• Setting requirements• Validates design• Approves change

Business analysts

• Gather requirements• Refines

requirements• Reviews change• Supports testing

Developers

• Leverages requirements for design and build

• Unit tests• Some integration tests• Writes test harnesses• Supports testing

Testers

• Validates requirements• Helps define quality

criteria• Designs test plans,

scripts• Executes tests• Regression test• Oversee UAT


Testing belongs to everyone – apply situational reality

Requirements

•Business: Sets expectations

•BAs: Refine expectations

•Developers: Translate expectations

•Testers: Question and validate expectations

Design

•Developers: Create the design

•Business validate design

•BAs: Validate design

•Testers: Verify impact and validate design

Developme

nt

•Developers: Create/integrate the application

•Business; Validate the application’s ability to meet requirements

•BAs – validate application meets requirements

•Testers: Validate requirements and expectations provide the greenlight






Recommendations

Agenda


Using tools to empower your teams

Project

planning

Requirements

definition

Requirements

management

Quality management

Change/risk management

Deployment planning

Analysis

Design

Build Configuration mgmt

Test Execution

Deployment preparation

UAT

BetaDeployment

Support

Plan Execute

Deploy


Tools can and will cut down schedule time if you plan carefully

• Sequenced testing by type

• Kicks off automation• Start regression plans

• Increases automation

through phases

• Describes what when how and why

• Provides sequence of testing

• Automation plans• Provides caveats

• Allocates testers and tests

• Prioritize tests• Provide date

constraints• Provides thresholds

• Provides ranges

Requirements

Test Plans

Phased testing

Regression






Recommendations

Agenda


Recommendations

Empowerment begins when you recognize QA as a profession

Start early and drive collaboration across the team from the requirements

process

Drive a team approach through processes and methodology

Tools will help – use them wisely – plan for business process driven

automation and use that to manage regression testing


Thank you

Margo Visitacion [email protected]

www.forrester.com


Questions?

Please type your

questions into the

chat window?


Thank You!

http://smartbear.com/products

do the right thing - empowering your test teams

Technology