CodeCampIasi25Oct2014

2. Quality Awareness
When Practicing Agile Testing
Ana Milutinovic, Quality Assurance Engineer @
YOUNGCULTURE
25th of October 2014

3. “Quality is a value to some person, at some time”
Jerry Weinberg
1. Understanding the impact of this statement
2. Going to effort of making every team member aware of this
concept

4. How did agile come around?
Deliver working software
frequently…
Daily whole team
collaboration…
Build projects around
motivated individuals…
Working software as the
primary measure of
progress…
Self-organizing teams…
Satisfied customers…

5. How it really looked
Go agile!

6. SCRUM Framework
Test management tool Defect tracking tool
Product backlog
Team 5 – 7 people
Sprint
2 weeks
First release after 1,5 year
Customer-ready
Product Increment
Project duration: 3 years and counting…

7. Problems
We were confused in Test
Planning
Sprints looked like small
Waterfalls
No time to test Bugs accumulating
QA was left out of the process.

8. Living in a time box

9. Quality in Planning
Ideas to improve Test Planning:
Parallel QA Sprint
QA in Poker Planning

10. Quality in Planning
3 8 5
QA
Poker Planning
“Everyone involved with delivering code is a developer, and is part of
the developer team.”
Lisa Crispin and Janet Gregory

11. Quality in Planning
Arguments for (not)involving QA into Poker Planning:
Symmetry
between testing
and
programming
Testing never
ends
Where is the
scope of
‘Done’
CD system
Programming
never ends
Agile implies
adjustments
QA was included
into calculation

12. Quality in Design
• Avoid presenting finished test cases to developers
• Create a common understanding of the user story, get
the right direction and split it into smaller pieces.
• Decision on which stories need automation.

13. Quality in Execution
IF IT CAN’T BE TESTED
IT’S NOT GOING INTO
SCRUM
AUTOMATION IN EACH
SPRINT
CONTINIOUS DELIVERY
TESTABLE USER STORIES
QA ESTIMATED
TEST AUTOMATION
AGREEMENT
CLEARLY ESTABLISHED
TEST GOALS

14. Quality in Reporting and Metrics
We allowed testing to be planned in fewer details.
Attention in reporting to whatever is specific for the
current sprint.

15. Quality in Reporting and Metrics
Test Planning
- Test strategy
- Story board
- Simple test management tool
Defect Tracking Tool
- Not track defect rates
- Attention on fast feedback
Sprint Review
- Discussion whatever defect influenced the sprint in an
interesting way

16. Agile in Fundamental Test Process
Planning
& Control
Analyses
& Design
Test
Closure
Reporting Execution

17. Thank You!