Mob programming is a software development approach where the entire team works together on the same feature at the same time. It is like a flock of birds flying in formation, where individuals take turns in leadership roles like "driver" who types code, and "navigators" who provide suggestions. Benefits include increased collaboration, shared understanding, knowledge transfer between junior and senior developers, and an environment where team members can easily help each other when stuck. Mob programming requires flexibility in changing roles and working styles.

1. The Mob Programming
What I have been learning from Woody Zuill

6. What Is Mob Programming?
A software development
approach where the whole
team works
on the same thing,
at the same time,
in the same space,
at the same computer

7. Driver
Navigator
Navigator
Navigator
Navigator

11. https://www.howitworksdaily.com/why-do-birds-flock-together

12. Leadership
• The V formation provides the birds with good
visual contact of each other
• A large or strong bird will take the lead.
Interpretation:
• The leader will lead by
example.
• V Formation = Everyone knows
where the heading
(transparency)
https://www.howitworksdaily.com/why-do-birds-flock-together

13. https://mobprogramming.org/mob-programming-basics/
Looking in the same direction
We know
where we go

14. Helpful Environment
Each bird will benefit from the updraft created by
the flapping of the bird in front’s wings (which
creates currents of circulating air), generating lift
for the birds behind to take advantage of.
Interpretation:
Everyone will get benefits
from the leader who
creates a helpful and safe
environment that can
leverage the productivity of
team as a whole
https://www.howitworksdaily.com/why-do-birds-flock-together
https://pixabay.com/photos/geese-birds-flock-wildlife-flying-1990202/

15. https://www.chrislucian.com/2016/05/mob-programming-q.html

16. Budget Environment 

17. Change Direction
When the flock changes direction, a new leader
will take the helm.
Interpretation:
When a new goal decided,
then the whole team change
the working direction to the
new goal.
Each team member has a
chance to learn to be a
leader and be a leader.
https://www.howitworksdaily.com/why-do-birds-flock-together
https://www.smithsonianmag.com/science-nature/how-just-one-bird-can-urge-entire-flock-change-directions-180952426/

18. The junior is trying
to lead
The senior as
driver. No thinking.

19. Rotation
If the leader becomes tired it will rotate back into
formation and another bird will then take the
lead.
Interpretation:
You can count on other
team members who will be
happy to help when you
are getting stuck or feel
unwell.
https://www.howitworksdaily.com/why-do-birds-flock-together
https://www.upi.com/Science_News/2015/02/03/Birds-take-turns-leading-migratory-V-formations/7751422995643/

20. Can’t sleep well
last night. Can you
replace me?
No worries

21. https://www.slideshare.net/andrefaria/mob-programming

22. Lag Behind
If a bird falls out of formation it will notice the
extra resistance and immediately get back in line.
Interpretation:
You know when you are
lagging behind. But you
can catch up fast because
you know where team is
heading.
https://www.howitworksdaily.com/why-do-birds-flock-together
https://www.natgeokids.com/za/discover/science/nature/birds-flock/

23. Newcomer

24. Sick Birds
A sick or wounded bird will drop out of formation
and one other bird will follow it until it recovers
or dies.
Interpretation:
Being accountable for each
other. Help the team
members to keep the skill
updated. It is about
growing together.
https://www.howitworksdaily.com/why-do-birds-flock-together

25. Mobbing
Navigator
Junior Middle Senior
Driver
Junior Clueless Teaching Mentoring
Middle Learning Production Mentoring
Senior Learning Production
Hyper
Production

26. Create a List of Productivity Destroyer

27. Productivity Destroyer
• Misinformation
• Missing Information
• Pressure
• Deadline
• Meeting
• Procrastination
• Distraction
• Interruptions
• Dependencies on
other
• Small screens
• Slow computer
• Relationship conflict
• Strict roles
• Process
• Dress code
• Technical debt
• Bugs
• JIRA

32. Approved by Gunther Verheyen

33. Extreme Scrum
• If planning is good, let’s do it every time
• If working as team is good, let’s do it every time
• If daily Scrum is good, let’s do it every time
• If frequent integration is good, let’s do it every time
• If frequent delivery is good, let’s do it every time
• If review is good, let’s do it every time
• If retrospective is good, let’s do it every time

34. Scrum
Just in Time
Planning
User Stories
Collective
Ownership
Planning Poker
Relative
Estimation
Release
PlanningPair
Programming
Mob
Programming
Information
Radiators
Burndown
Charts
Specification
by Example
Continuous
Integration
Continuous
Delivery
Build
Automation
Test Driven
Development
Continuous
Deployment
Design for
Operations
Refactoring
Clean Code
Design
Patterns
Reducing
Technical Debt
Emergent
Architecture
Executable
Specifications
ATDD
BDD
Scrum Guide People Practices
Engineering
Practices

35. https://leanpub.com/mobprogramming
https://mobprogramming.org/