agile testing in enterprise: way to transform - sqa days 2014
TRANSCRIPT
Agile Testing in Enterprise: Way to transform
Andrei RebrovAgile Coach
Disclaimer
Our waypoints
Table of content
• “True Story”• What kind of problems do we usually
notice• What kind of problems really happens• How to change your process• Good practices• Next steps
“True story”
Story #1
• Prerequisites:– 1 dev team– 2 QA engineers
• Problems:– long regression cycle– unmet estimates– low product quality– total stress
Story # 2
• Prerequisites– huge bank with its own culture– testing performed by BA– chaos
• Problems:– low product quality– slow delivery– unstable infrastructure
Why does company need to change?It’s cool We have budget
Conference talk We want to survive
Business need it
What business doesn’t like
• estimates and delivery speed• vendor’s bureaucracy• no ways to experiment
Let’s talk about IT
• Business wants everything and right now• No way for growth• Need in building high quality products
What IT doesn’t like
We need perfect World!
But to be honest, we want…
• Get right product• In predictable time and quality• Improve team and product
Time to cure
Root cause
• document-based collaboration• developers don’t know about testing
practices• chaos in infrastructure management• work time utilization - ‐> no time for
improvement
Let’s start from scratch
Untranslated Russian joke, saying«Don’t call your laziness corporate culture»
What is quality
Maslow’s Hierarchy of Needs
Gojko Adzic Quality Hierarchy
Kanban to Focus
Collaboration during BA
Team should know what to test
Time to manage risks
Easiest way
Risks in QA
• Infrastructure denial• Bus factor• Test automation engineer who likes
snowboarding
Continuous Quality
Тестирование и DevOps
Culture Automation
Measurement Sharing
Summary
• Kanban to help us synchronize and collaborate• Common work on requirements• Smart quality metrics• Test Automation • Agile testing quadrant model as whole team
approach for testing• DevOps approach to manage infrastucture
What we implemented
• Risk management• Spec By Example• TDD + Integration testing (test
automation pyramid)• Continuous Integration• Automation configuration• Test automation• Proactive monitoring
Implemented practices
What do we have now
• Delivery rate increased up to 5 times• 2-3 delivery every weak• Zero bugs in productions• No more overtimes• Work became enjoyable
Next steps
• Mentorship• Usability testing• Non functional testing• Engineer in test
