W6

Special Topics

5/7/2014 11:30:00 AM

Test Process Improvement in

Agile

Presented by:

Jeroen Mengerink

Polteq

Brought to you by:

340 Corporate Way, Suite 300, Orange Park, FL 32073

888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com

Jeroen Mengerink

Polteq

As a test consultant for the Netherlands-based Polteq Test Services B.V. Jeroen Mengerink has performed multiple TPI assessments worldwide. His technical skills allow him to team with developers in testing websites, APIs, and web services. Jeroen performs both functional testing and performance testing. In addition to his work for clients, he is involved within various test innovations in the area of agile. Jeroen teaches the Certified Agile Tester course and several test courses on agile, SOA, and cloud; coauthored Testing Cloud Services; and blogs at jmengerink.wordpress.com. Follow him on Twitter @AngusVB.Â

26-4-2014

© Polteq 1

Test process improvement in Agile

Jeroen Mengerink

@AngusVBwww.polteq.com

jmengerink.wordpress.com

2© 2014

Current TPI models

Focus on:

• Testing

• Bringing structure

• Traditional development

26-4-2014

© Polteq 2

3© 2014

PerformingNormingForming .

Evolution of Agile testing

Pioneering

Structured

Agile

Time

Structured �

�Not structured

4© 2014

Agile testing maturity levels

Forming Norming Performing

Agile testing levels

Set the basis and the first steps towards working in an Agile manner

Adopt a process that facilitates the Agile view on working

Continuously improve the way you work by living the Agile way

26-4-2014

© Polteq 3

5© 2014

Roadmap

Quick wins,

good practices

Goals, scope

Interviews,

meetings

Assessment

Awareness,

commitment,

buy-inImplement and evaluate

6© 2014

Assessment model

Key area Forming Norming Performing

1 Stakeholder commitment

2 Planning & Estimation

3 People

4 Interaction

5 Teamwork

6 Test process

7 Test management

8 Test profession

9 Test automation

10 Regression & E2E testing

11 Defect management

12 Test environment

26-4-2014

© Polteq 4

7© 2014

Assessment model: example result

Key area Forming Norming Performing

1 Stakeholder commitment 1 2 3 4 1 2 3 4 1 2 3

2 Planning & Estimation 1 2 3 4 1 2 3 4 1 2 3 4

3 People 1 2 3 4 1 2 3 4 1 2 3

4 Interaction 1 2 3 4 1 2 3 4 1 2 3 4

5 Teamwork 1 2 3 1 2 3 4 1 2 3 4

6 Test process 1 2 3 1 2 3 4 1 2 3

7 Test management 1 2 3 4 1 2 3 1 2 3

8 Test profession 1 2 3 4 1 2 3 1 2 3 4

9 Test automation 1 2 3 1 2 3 4 1 2 3 4

10 Regression & E2E testing 1 2 3 4 1 2 3 1 2 3 4

11 Defect management 1 2 3 1 2 3 4 1 2 3

12 Test environment 1 2 3 1 2 3 1 2 3 4

8© 2014

Teamwork

Forming Norming Performing

TI4Agile

The team executes a task

The team is committed

The team is self managing

26-4-2014

© Polteq 5

9© 2014

Teamwork - Multi disciplinary

• Everyone has his own specialization

• Think from the perspective of other roles

• Assist each other where possible

• Communicate your expectations

Tester

Developer

Designer

Customer

10© 2014

Teamwork - Team development

26-4-2014

© Polteq 6

11© 2014

Teamwork - Keep the goal visible

12© 2014

Test management

Forming Norming Performing

TI4Agile

Genericapproach

Support the process

Support the people

26-4-2014

© Polteq 7

13© 2014

Test management –Generic test approach / strategy

• Training and coaching

• Defect management

• Risk analysis

• Non-functionals

• E2E testing

• Tooling and automation

• Environment management

• Metrics and reporting

• …

14© 2014

Generic test approach / strategy

RisksMaturitySkills

ProductSizeTime

Culture

Bandwidth

Bandwidth

Test management –Generic test approach / strategy

26-4-2014

© Polteq 8

15© 2014

Test management - Risks

CoreNot every adjustmenthas an equal impact

Layer 1

Layer 2

16© 2014

Test management - Risks

Core

Core:

Technical:

- Database interaction

- Most used DLL’s

Functional:

- Most important proces

- Most used functionality

Impact : Huge

Core

Layer 2

Layer 1

26-4-2014

© Polteq 9

17© 2014

Test management - Risks

Core

Center layer(s):

Technical:

- Algorithms

- APIs

Functional:

- Often used processes

- Important functionality

Impact : Middle

Core

Layer 2

Layer 1

18© 2014

Test management - Risks

Core

Layer 1

Layer 2

Impact : Small

Outer layer(s):

Technical:

- Screens / fields

- Views

- Forms

Functional:

- Little used processes

- Less used functionalityCore

26-4-2014

© Polteq 10

19© 2014

Regression & E2E testing

Forming Norming Performing

TI4Agile

In focusAs well in as over iterations

Proactively addressed

20© 2014

Regression & E2E testing - Mind mapping

• Visualize information in a structured way

• Create a clear view on E2E information

– Which parts are done?

– Which risks are involved?

– How to test?

• Understandable for different types of people

26-4-2014

© Polteq 11

21© 2014

Regression & E2E testing - Mind mapping

22© 2014

Regression & E2E testing –Coping with regression

• Hardening iteration

– Iteration focused on improving the product

• E2E

• Regression

• Loose ends

• Shortcuts

• Non-functionals

– Should be used as little as possible

26-4-2014

© Polteq 12

23© 2014

Conclusion

For test improvement in Agile we focus on:

– People

– Development process

– Testing

Know your structured basis and apply it flexible