Mob review at Akeneo

How and why we changed our way to review code at Akeneo. Our path from almost no code review to mob review.

Transcript

1. Mob review at 3+ (wo)men, 1 laptop presented by Ju&Ju
2. 2013 - no or optional code review
3. 2014 - systematic peer review
4. Systematic & public
5. Good To Merge
6. OK, problem solved?
7. Well… nope :)
8. 2015 - team/product growing
9. Problems - A lot of comments
10. Problem - Not focused on what’s important
11. Problems - Long exchanges
12. Problems - Misunderstandings with non verbal communication
13. Github + many people => code review (not for us)
14. Interactions >>> Tools
15. 2016 - introducing mob review
16. Mob programming is a software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer.
17. Mob programming review is a software development approach where the whole team works on reviews the same thing, at the same time, in the same space, and at the same computer.
18. Informal & public
20. Used only for “specific” topics
21. Pros & cons
22. Pros • Easy to setup • 0€ to setup • Exchanges facilitated, less frustration • Merge faster, less returns • Knowledge is really shared • Focus on what really matters • Share a common technical vision • Responsibility even more shared
23. Cons • Beware to not talk about something else • Can’t put GIF anymore in the PRs :’( • Sometimes hard to find reviewers • Sometimes too much to review
24. Tomorrow?
25. Mob review at Questions?