Hinweis: Die aktuelle OOP-Konferenz finden Sie hier!
SIGS DATACOM Fachinformationen für IT-Professionals

SOFTWARE MEETS BUSINESS:
Die Konferenz für Software-Architekturen
30. Januar - 03. Februar 2017

Sessionsdetails

Vortrag: Mi 5.4
Datum: Mi, 01.02.2017
Uhrzeit: 17:00 - 18:00
cart

Sharing the quality responsibility in agile teams

Uhrzeit: 17:00 - 18:00
Vortrag: Mi 5.4

 

Successful agile teams live and work by the principle of “whole team quality”. This doesn’t necessarily mean that everyone is responsible for everything in terms of quality, but it does mean that everyone is responsible for the overall quality. It makes sense to empower teams to undertake quality tasks as a team – and not leave them to selected people.
In this talk, I present the techniques we use to evolve our tester and developer roles when it comes to quality – without suggesting that the roles should necessarily merge.

Target Audience: test managers, agile practitioners, scrum masters, testers, developers
Prerequisites: Basics of agile and scrum
Level: Practicing

Extended Abstract
Successful agile teams live and work by the principle of “whole team quality”. This doesn’t necessarily mean that everyone is responsible for everything in terms of quality, but it does mean that everyone is responsible for the overall quality. It makes sense to enable and empower teams to undertake quality tasks as a team – and not just leave them to selected people.
In this talk, I’ll present the techniques we use to evolve our tester and developer roles to bring them closer together when it comes to quality – without suggesting that the roles should necessarily merge. I’ll talk about:
• Training testers and developers in exploratory testing techniques
• Focusing the team on ‘getting things done’ (where done is also tested!)
• Refining the tester role into more technical and more functional aspects
• Business-facing test automation and how teams can successfully distribute the work involved
o Including the concepts of “technical quality advocates” and “Java for Testers”
• Automation Patterns for business-facing test automation
• Seamless integration of test automation into the daily life of the team
• Moving from Continuous Integration to Continuous (Internal) Deployment to more frequent external releases
I’ll start with an explanation of our history and status quo as an example of techniques and practices that need to be in place, then introduce the drivers for making changes before presenting the individual practices and their effects.