from mini waterfall to Scrum by adopting Agile testing practices

1. A Path of Improvements and Adjustments
From Mini Waterfall To
Scrum
Thessaloniki’s Agile & Lean meetup, 7/4/2017,
Nick Meggoudis, Product Owner, Agile Enthusiast

2. • Introduction
• How we worked
• Defining the issues
• Preparation
• Steps followed
• Results
Topics

3. Introduction
What is this presentation about?
• The side effects of adopting partially the Scrum framework
• Practices that helped to overcome those issues
• Impact after actual embracing them

4. Introduction
The trigger
Size does matters
An enterprise platform containing 9 different applications
Near to 300k lines of code
More than 10k unit tests
5 additional applications should be production ready after 9 months 

5. How we worked
What we followed at that time
Extreme Programming
• Test driven development
• Pair programming
• Design improvement
• Continuous integration
• …
Scrum
• Daily Scrum
• Sprints
• Sprint Planning
Unified
• …

6. How we worked
What we followed at that time
Developers Testers
Backlog

7. Defining the issues
Side effects
0
50
100
150
200
250
0 5 10 15 20 25 30
Fixed
Found
Bugs Per Month

8. Defining the issues
Side effects

9. How we worked
What We Followed At That Time
~Extreme Programming
•…
Scrum
• …
Unified
• …
Mini Waterfall
NOPE

10. Preparation
For Two Weeks
Full Test
Found Fixed
Reviewed

11. Steps followed
Definition of Done
•“Defining done makes the work/steps obvious and therefore we gain awarene
ss…”
• Bulwark against debt building up
• Kanban board
• Work In Progress reduction

12. Steps followed
Bring Testing Close To Development

13. Steps followed
Bring Testing Even Closer

14. How we worked
What To Avoid
Developers Testers

15. Steps followed
Cross Functional Team Formation
Development Team
Backlog

16. Steps followed
Test Automations

17. Steps followed
Make Changes In Scope
• "special sprints“ is an antipattern

18. Results
Bugs reduction
• The number of bugs
• The first bug-less User Stories (5 of 14)
• The stable average time of bug fix
• Fixed bugs followed the bugs found
• Technical dept reduction

19. Results
Bugs AVG Hours
0
1
2
3
4
5
6
7
8
0 5 10 15 20 25 30 35 40
AVG Hours

20. Results
Bugs Found/Fixed
0 5 10 15 20 25 30 35 40
Found
Fixed
Fixed
Found

21. Results
Cumulative Per Month
0
20
40
60
80
100
120
2016 11 2016 12 2017 01 2017 02 2017 03
Production
Documented
Accepted
Testing
Developed

22. Results
User Stories Burn up Chart
0
20
40
60
80
100
120
140
0 1 2 3 4 5 6 7
Features

23. Results
Releases
0
20
40
60
80
100
120
Total
Test
Production

24. Conclusion
Take Risk by Making Changes
Each change has a risk but it is something that worth to take. Agile frameworks
like Scrum, reduces the risk within small iterations.
Fail Fast, Fail Often…

25. Thank You All…!!!
The case study can be also found online at nmeggoudis.org
and agilegreece.org