+ All Categories
Home > Documents > Btd erik bits bernd beersma 1.4

Btd erik bits bernd beersma 1.4

Date post: 14-Jul-2015
Category:
Upload: bernd-beersma
View: 250 times
Download: 3 times
Share this document with a friend
Popular Tags:
32
#SQASC Setting up an Agile Support Center for Test & Maintenance #SQASC
Transcript

#SQASC

Setting up

an Agile Support Center

for Test & Maintenance

#SQASC

#SQASC

e: [email protected] m: +31 6-11010659 tw: @bbeersma

Expertise Manager Test Automation

10+ years of experience in TA & PT

Senior Automation Specialist

Board Member ATI Europe

Initiator Test Automation Day

#SQASC

Expertise Manager Testing

10+ years of experience in Testing

Senior Test Manager

Trainer

e: [email protected] m: +31 6- 10157172 tw: @erikbits

#SQASC

Increasing test

effort

Testing versus

Checking

Functionality

versus

characteristics

Waterfall

versus Agile

Product backlog

#SQASC #SQASC Waterfall versus Agile

#SQASC Waterfall versus Agile

Individuals and interactions

Over

Working software

Over

Over Customer

collaboration

Responding to change

Over

Process and tools

Comprehensive documentation

Contract negotiation

Following a plan

#SQASC

#SQASC Benefits of Agile

Earlier involvement of testers in the project

Boundaries between test & development vanish

Joint quality awareness

Flexible approach

#SQASC Risks caused by Agile

Focus on functionality

Limited knowledge of test automation

Joint quality responsibility

Changing requirements, flexible approach

Lack of documentation

Testing ‘what is’ instead of ‘what is expected’

Increasing test effort

#SQASC Increasing test effort

#SQASC

1.

2.

3.

4.

5.

Limited knowledge of TA within the teams

Scope creep from ICT & Process to ICT

Increasing test effort

We need test automation

Backlog sprint 1

Focus on functionality

#SQASC Agile Support Center

Iteration 0

Agile Support Center

Sprint 1 Sprint 3 Sprint 2 Hardening

Ticket

Ticket

Maintenance

Departement

Regression Sprint 2

Regression Sprint 1

Checklist

Single Point of Communication (ASC)

All communication between the ASC and the Scrum

team takes place via one person. This person also

participates in the planning sessions

Tickets Tickets Tickets

Ticket: This is a (test) work assignment in response to a perceived risk of a quality attribute (functional or characteristic) A ticket passes the following phases: 1. New: A ticket is submitted to the ASC 2. Approved: A ticket is accepted by the ASC 3. Analyzed: The ASC has determined the impact,

the approach and turnaround. 4. Scheduled: The ticket is scheduled 5. Started: The test activities are being executed 6. Executed: The test is performed 7. Delivered: The ticket is transferred to the sprint

team

#SQASC Ticket = mini-testplan

#SQASC

#SQASC Ticket = mini-testplan

#SQASC

#SQASC

1.

2.

3.

4.

5.

Limited knowledge of TA within the teams

Scope creep from ICT & Process to ICT

Increasing test effort

We need test automation

Definition of Done

Focus on functionality

#SQASC

Increasing test

effort

Testing versus

Checking

Functionality

versus

characteristics

Waterfall

versus Agile

Product backlog

#SQASC

Testing versus Checking

#SQASC

<Y2K

Functionality versus characteristics

#SQASC Functionality versus characteristics

#SQASC Functionality versus characteristics

#SQASC Functionality versus characteristics

#SQASC

Functionality is still important,

characteristics are increasingly

important……..

Functionality versus characteristics

#SQASC

9126

Maintainability

Portability

Efficiency

Functionality

Reliability

Usability

ISO 9126 ISO 25010

#SQASC

25010

Maintainability

Portability

Performance Efficiency

Functional Suitability

Reliability

Usability

ISO 9126 ISO 25010

#SQASC

25010 Maintainability

Portability

Performance Efficiency

Compatibility Functional Suitability

Reliability

Usability

ISO 9126 ISO 25010

#SQASC

25010 Maintainability

Portability

Performance Efficiency

Security

Compatibility

Functional Suitability

Reliability

Usability

ISO 9126 ISO 25010

#SQASC

1.

2.

3.

4.

5.

Awareness is created, but what about execution?

Not all tests can be automated, still manual tests

Shift from functionality to characteristics

Limited knowledge of characteristics in the teams

Backlog sprint 2

Synchronization between ASC and Scrum team

#SQASC Agile Support Center

Iteration 0

Agile Support Center

Sprint 1 Sprint 3 Sprint 2

Ticket

Ticket

Maintenance

Departement

Regression Sprint 2

Regression Sprint 1

Checklist

Single Point of Communication (ASC)

Tickets Tickets Tickets

SecurityTest Sprint 1 SecurityTest Sprint 2

Performance Test Sprint 1

Tickets

Aut. Regression

Testing

Performance

Testing

Security

Testing

Test

Environment Other

Process:

☑ The SPOC brings the

characteristics to the attention

☑ determine initial test capacity

☑ determine initial planning

☑ adjust / calibrate the planning

according to sprint backlogs

☑ Preparation of the detailed

planning based on the Agile

tickets

☑ Periodic evaluation and

adjustment

#SQASC

1.

2.

3.

4.

5.

Awareness is created, but what about execution?

Not all tests can be automated, still manual tests

Shift from functionality to characteristics

Limited knowledge of characteristics in the teams

Definition of Done

Synchronization between ASC and Scrum team

#SQASC

Increasing test

effort

Testing versus

Checking

Functionality

versus

characteristics

Waterfall

versus Agile

Product backlog

#SQASC 3 Good reasons for an ASC

#SQASC For Whom (what’s in it for me)?

Size does not matter

The amount of work does

How to organize?

#SQASC

Reuse of knowledge

Efficient use of

Available time

Reuse of testware

Reuse of tooling

Flexible

resourcing

Insourcing

Outsourcing

For everyone

Hybrid

Central Testware

mgmt

#SQASC


Recommended