A copyright of Ram Yonish. Do not use without an explicit permission

Vgile

Risk Based

Agile

V-model

ryonish@tact.co.il

My self

My company

My idea

3

Agenda

Basic assumptions & Motivation

Traditional vs. Current trends

Case study - example

Risk based testing

Vgile concept

Vgile best practices

summary

4

Basic assumptions & Motivation

Flexible systems

• More competition requires more flexible & reliable systems = much more features and changes in a shorter time frame

Vmodel

• Vmodel is the most common L.C development model

• Many organizations want to stay with Vmodel

Agile

• Many organizations are interested in Agile but afraid to make a dramatic move towards such a model

???

5

Many types of life cycles to choose from 1/2

serial iterative incremental agile

V model

waterfall spiral Design to

schedulescrum

© 2008 Johanna Rothman

http://www.jrothman.com/Papers/Cutter/whatlifecycle.html

A cynical senior manager said, “It feels as if I‟m stuck between

the traditionalists and the agilistas. We can‟t use phase-gate

anymore, because it‟s not „agile‟ enough. And the last time,

when that multisite project tried Scrum, they failed miserably.

Isn‟t there a right approach to our projects?”

XP

6

Many types of life cycles to choose from 2/2

7

Traditional vs. Current trends

“There are still

no silver bullets,

but we can

accept that

there are new

kinds of regular

bullets

available”

Richard Turner (cmmi & agile expert) Turner.html0704/04/2007http://www.stsc.hill.af.mil/CrossTalk/

8

Case study - what do you think?

100 < new features/ changes per version (all have FD)

1:5 testers/ developers ratio (5-10 testers)

A version every 4-6 weeks

STP?

Reviews?

STD?

Scripted testing?

Test coverage?

Exit/ entry criteria?

Classic/ modern

techniques?

What would you do?

9

Risk based testing

The amount of testing is based on “feature risk level”

The feature owner/ designer determine the “risk level”

Risk level 1: STP, reviews, simulations, scripted testing, high

coverage (100% successful testing) and documentation. Vgile teams

Risk level 2: medium coverage (80% successful testing) and doc’

Risk level 3: low coverage (50% successful testing) no doc’, Mainly

exploratory testing.

10

Testing Highlights

Develop a generic list (use brain storming)

Adjust according to the specific version/ feature

Part of the design document (Responsibility of the designer)

Early in the process (prevention activity):

Better design

Basis for dev testing

Skeleton for STP (what to test)

Example

11

Vgile concept

Design Development Validation

Product

Development

Business, Technology, Standards & regulations

Test

Dev‟

Test

Business, Technology, Standards & regulations

Product

Test

Product

Business, Technology, Standards & regulations

Development

A classic “serial” life cycle

Different owner for different feature life cycle phase

12

Vgile - the PDT triangle

Product

Development

Business, Technology, Standards & regulations

Test

Small team:

Product/Feature owner (designer, product manager, user)

Developer

Tester

Team responsibility for a feature L.C

Team member leader according to the

development phase

Team activities: review, dry run, unit, simulations,

integration and system testing

More than one feature per every team

13

Vgile - best practices

Product

Developer

Business, Technology, Standards & regulations

Tester

Max 3 months for every release

Weekly meetings (also by remote access tools)

“KISS” - hands on, short, just enough doc‟

In addition to traditional QA methodologies:

Unit & Integration test by developers ( also: continues

integration, nightly builds, TDD)

Entry & Exit criteria

Test documentation (STP, STD, STR)

Risk based testing

Static testing (e.g. early test design)

14

Vgile - the PDT triangle HEART

Business, Technology, Standards

& regulations

Every action in every phase should be monitored

and reviewed based on 3 essentials:

Business: understand your users and business

process

Technology: understand your environment, hardware

and software issues, system architecture and user

configurations

Standards & Regulations: understand

industry standards, organization policy and

regulations, measurements & metrics

15

Vgile concept conclusion

Based on the V model “serial” LC process

Risk based testing & prevention activities

Agile elements:

More communication

Team responsibility

16

I’m not alone, this is what Forrester have to say aboutMixing methodologies (January 20, 2010 )

17

References

“agile development mainstream adoption has

changed agility”, Forrester - Dave west and Tom grant, January

20, 2010

“Testing and scrum”, van roosmalen, fall 2007

“What Lifecycle? Selecting the Right Model for Your

Project”, Johanna Rothman, 2008

“Toward Agile Systems Engineering Processes”, Dr. Richard Turner, Systems and Software Consortium, April 2007

“A Few Good (Agile) Testers - Introducing Agile Testing

Brings Quality Without An Army Of Testers”, Forrester - Margo

Visitacion VP, December 18, 2009

18

Vgile methodology

Easy to understand

Easy to implement

Easy to maintain

Thanks

ryonish@tact.co.il

www.tact.co.il