SlideShare a Scribd company logo

Some Helpful Observations for successful Mob Programming

•Download as PPTX, PDF•
•
Llewellyn Falco
Llewellyn Falco

The document provides several observations for successful mob programming: - Always be actively contributing to the mob in any way possible, such as navigation, proofreading, asking questions, or offering suggestions. - Respect each other's strengths and weaknesses as individuals and as the group works together to learn. - Respect the existing code while still looking to improve it, without insulting previous work and thoughtfully navigating changes.

Related slideshows

A class action
A class actionA class action
A class action
 
Confessions of a Flow Junkie
Confessions of a Flow JunkieConfessions of a Flow Junkie
Confessions of a Flow Junkie
 
Growing Your User Group
Growing Your User GroupGrowing Your User Group
Growing Your User Group
 
1 of 7
SOME HELPFUL OBSERVATIONS FOR SUCCESSFUL MOB PROGRAMMING From The Hunter Mob & Llewellyn Falco
There are many ways to contribute. Navigation & Driving is obvious, but there is also proof reading, googling, sharing shortcuts, offering affirmations & suggestions; even asking “why?” can be helpful. Always find your way to be actively contributing to the mob. ALWAYS BE CONTRIBUTING
We all have our strengths and weakness. In the exposure of the mob, we value each others strengths, forgive each others weakness and are patience with each other as we learn. RESPECT EACH OTHER
The code is never perfect and we are always looking to make it better. However, we respect the value the current code brings, and the effort needed to get the code to it’s current level. This means not insulting the previous creators but also that when you navigate you work with the code and don’t just remove what the previous person did. RESPECT THE CODE
If there are 2 solutions, just pick 1 and try it. Afterwards, you can discuss if you need to go back and try the other one instead. Many times, form the perspective of a finished task, people no longer care. If you still do, then it probably is important to try the other path. But never spend 20 minutes discussing something that can be done in 10. JUST TRY IT
We always strive to speak at the highest level the diver can understand. This will change by person and even by time of day. Sometimes the diver can understand “loop thru that list”, sometimes “write a for loop” and sometimes we will need the keystrokes “f-o-r”. The navigators take care to keep their communications as high as possible while still within the drivers immediate understanding. SPEAK TO THE DRIVER
The environment should service being an active part of the mob. This means valuing comfort and other human factors but also means that sometimes you will need a short break. Don’t be afraid to take one, the flow of the mob and the work will continue without you and be here ready for you when you return. DON’T BE AFRAID TO TAKE A BIO-BREAK

More Related Content

Some Helpful Observations for successful Mob Programming

  • 1. SOME HELPFUL OBSERVATIONS FOR SUCCESSFUL MOB PROGRAMMING From The Hunter Mob & Llewellyn Falco
  • 2. There are many ways to contribute. Navigation & Driving is obvious, but there is also proof reading, googling, sharing shortcuts, offering affirmations & suggestions; even asking “why?” can be helpful. Always find your way to be actively contributing to the mob. ALWAYS BE CONTRIBUTING
  • 3. We all have our strengths and weakness. In the exposure of the mob, we value each others strengths, forgive each others weakness and are patience with each other as we learn. RESPECT EACH OTHER
  • 4. The code is never perfect and we are always looking to make it better. However, we respect the value the current code brings, and the effort needed to get the code to it’s current level. This means not insulting the previous creators but also that when you navigate you work with the code and don’t just remove what the previous person did. RESPECT THE CODE
  • 5. If there are 2 solutions, just pick 1 and try it. Afterwards, you can discuss if you need to go back and try the other one instead. Many times, form the perspective of a finished task, people no longer care. If you still do, then it probably is important to try the other path. But never spend 20 minutes discussing something that can be done in 10. JUST TRY IT
  • 6. We always strive to speak at the highest level the diver can understand. This will change by person and even by time of day. Sometimes the diver can understand “loop thru that list”, sometimes “write a for loop” and sometimes we will need the keystrokes “f-o-r”. The navigators take care to keep their communications as high as possible while still within the drivers immediate understanding. SPEAK TO THE DRIVER
  • 7. The environment should service being an active part of the mob. This means valuing comfort and other human factors but also means that sometimes you will need a short break. Don’t be afraid to take one, the flow of the mob and the work will continue without you and be here ready for you when you return. DON’T BE AFRAID TO TAKE A BIO-BREAK