When I was an Engineering Manager at CoachHub, pairing and mob programming quickly became second nature to the teams I worked with. It reached a point where I didn’t even have to advocate for it — engineers took full ownership of how, when, and how often they paired. They adjusted the style, session length, and group size themselves — because they saw the benefits firsthand: better code, deeper collaboration, and faster onboarding.

Later, when I joined Ogury as an Agile Coach, I was surprised to face almost hostile reactions when suggesting pair or mob programming. For many, it seemed like a waste of time — something that would hurt productivity rather than help it. But as I dug deeper, I realized those concerns were valid: pairing had been misunderstood, misapplied, or imposed without context.

This talk is based on the presentation that helped me begin shifting that mindset across engineering and product teams. Aimed at Scrum Masters, Engineering Managers, team leads and engineers, it’s not just about explaining what pairing is — it’s about why it works, where it helps, and how to implement it without backlash.

You’ll walk away with:
- A deeper understanding of the real value of pair and mob programming
- Practical, battle-tested tips for introducing it with less resistance
- A human-centered perspective on collaboration, trust, and technical excellence

Whether you’re looking to bring pairing into your team — or just do it better — this talk will give you the tools (and the mindset) to make it happen.