«from waterfall to agile/scrum: the impact on testing»

FROM WATERFALL TO AGILE/SCRUM: IMPACT

ON TESTING

TRADITIONAL DEVELOPMENT

• KNOWING EVERYTHING

• FIXED REQUIREMENTS, ESTIMATES AND RESOURCES

• FREEZING REQUIREMENTS

• STATUS MEASURED

• WORKING SOFTWARE AT THE END OF DEVELOPMENT LIFECYCLE

AGILE METHODOLOGIES

Process and Tools

Comprehensive Documentation

Following Plan

Contract Negotiation

Individuals & Interaction

Working Software

Responding to Change

Customer Collaboration

Teamwork and Responsibility

Business value

Partnership Elaboration

Prepare for Change

TRADITIONAL DEVELOPMENT

MANAGEMENT

Traditional DevelopmentAgile/SCRUM

Command and

Control

Collaborative

Leadership

TEST MANAGER

Traditional DevelopmentAgile/SCRUM

Test Strateg

y

Test Plan

Product Risks

Test Estimati

on

Resources

...

Planning &

estimation

Detailed Product

risks Analysis

How to get right tester?

How to keep

testing knowledge up-to-date?

Info out of the team –

eye view on testing process

…

TESTER

Traditional DevelopmentAgile/SCRUM

Requirements analysis

Test Documentat

ion

Requirements

Analysis

Communication

Testing

Estimating

Test Documenta

tionTesting/

Regression/Automation

…

CHANGING ROLE OF TESTER

Traditional DevelopmentAgile/SCRUM

Work in team of testing prof’s

Role predominantly involves

testing

Last line of defense for software

quality

Test case prepared from well

documented req’s and designs

Clearly defined entry and exit

criteria

Work in cross functional team of analysts, developers, testers …

Expanded role - design

def/review, write/review code

and testing Quality responsibility of entire

sprint team Test cases prepared from user

stories, req. & design discussions, minimal docs

Testing is collaborative effort with other functions, no phase gate

CHANGING ROLE OF TESTER

Traditional DevelopmentAgile/SCRUM

Test execution after code

complete

Testing essentially Top-Down

Minimal involvement in Unit

testing

System level Automation test

scripts, after code is stabilized

Report progress by testing

phase

Iterative testing by feature and

not entire project

Testing essentially Bottom-Up

Active participation in Unit

testing

Automation from unit testing

level

Report progress by Feature

complete rather than testing

completion

KEY SUCCESS FACTOR

Test in small but do not lose sight of big picture

Ability to work in team and to get things dove

Communication and Collaboration

Comfortable with speed and just in time delivery

Design and Coding skills, at minimum - good analytical and review skill

Minimal reliance on documentary support

Focus on project deliverable, not on phase deliverables

QUESTIONS ?

Thank You!

Any Questions?

Thank You!

Any Questions?