setting up an agile support center expoqa 2014 bernd beersma and erik bits
TRANSCRIPT
Madrid, 26th to 28th May 2014
Setting up an Agile Support
Center
For Test and
Maintenance
Departments
Madrid, 26th to 28th May 2014
PLANNED IN PROGRESS DONE
Functionality
vs
Characteristics
Testing vs
Checking
Increasing
Test Effort
Waterfall versus Agile
Waterfall versus
Agile
Madrid, 26th to 28th May 2014
Waterfall versus Agile
Madrid, 26th to 28th May 2014
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
Madrid, 26th to 28th May 2014
Benefits caused by Agile
Earlier involvement of testers in the project
Flexible approach
Boundaries between test & development vanish
Joint quality awareness
Madrid, 26th to 28th May 2014
Risks caused by Agile
Lack of documentation
Changing requirements, flexible approach
Testing ‘what is’ instead of ‘what is expected’
Joint quality responsibility
Focus on functionality
Limited knowledge of test automation
Increasing test effort
Madrid, 26th to 28th May 2014
Increasing test effort
Madrid, 26th to 28th May 2014
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
Madrid, 26th to 28th May 2014
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
Hardening
Madrid, 26th to 28th May 2014
Ticket = mini-testplan
Madrid, 26th to 28th May 2014
Ticket = mini-testplan
Madrid, 26th to 28th May 2014
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
Madrid, 26th to 28th May 2014
PLANNED IN PROGRESS DONE
Functionality
vs
Characteristics
Testing vs
Checking
Increasing
Test Effort
Product Backlog
Waterfall versus
Agile
Madrid, 26th to 28th May 2014
Testing versus Checking
Madrid, 26th to 28th May 2014
Functionality versus characteristics
Functionality is
still important,
Characteristics
are increasingly
important……
Madrid, 26th to 28th May 2014
9126
Maintainability
Portability
Efficiency
Functionality
Reliability
Usability
ISO 9126 -> ISO 25010
Madrid, 26th to 28th May 2014
25010 Maintainability
Portability
Performance Efficiency
Security
Compatibility
Functional Suitability
Reliability
Usability
ISO 9126 -> ISO 25010
Madrid, 26th to 28th May 2014
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
Madrid, 26th to 28th May 2014
Agile Support Center
SecurityTest Sprint 1 SecurityTest Sprint 2
Performance Test Sprint 1
Tickets
Aut. Regression
Testing
Performance
Testing
Security
Testing
Test
Environment Other
Agile Support Center
Iteration 0 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
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
Madrid, 26th to 28th May 2014
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
Synchronization between ASC and Scrum team
Definition of Done
Madrid, 26th to 28th May 2014
PLANNED IN PROGRESS DONE
Functionality
vs
Characteristics
Testing vs
Checking
Increasing
Test Effort
Product Backlog
Waterfall versus
Agile
Madrid, 26th to 28th May 2014
3 Good reasons for an ASC
Madrid, 26th to 28th May 2014
Reuse of
knowledge
Reuse of
Testware
Central
Testware
management
Flexibele
Resourcing
Efficient use of
available time
For Whom (what’s in it for me)?
Reuse of
Tooling
Madrid, 26th to 28th May 2014
Madrid, 26th to 28th May 2014