Skip to main content

2021-11-28 Remote Mob Programming Training Report

· 3 min read
hoh
hoh

I attended the following training session:

[CodeZine Academy 11/28 (Thu) Event]
Remote Mob Programming Training with a Team
Link

Trainers​

  1. Yasui (Yattomu)
  2. Obu

Tools Used​

  1. repl.it
    1. Link
    2. An online service for sharing code editors
  2. mural
    1. Used for Q&A and task management
  3. Mob Timer
    1. Link
  1. Remote Mob Programming - STAY HOME with TEAM
  2. Published Video on Online Mob Programming #SilverBulletTV

Q&A​

  1. ❓ How do you decide the driver rotation order?

    • 🅰️ Shuffling generally works well.
      • Using a timer for switching is best practice.
      • Avoiding strict rules makes transitions smoother.
      • More experienced teams may use a voluntary system.

  2. ❓ Why do drivers need to switch?

    • 🅰️ Since drivers focus on writing code, they struggle with understanding and thinking simultaneously.
      • Rotating and expressing gratitude is important.

  3. ❓ What is the optimal team size?

    • 🅰️ It depends on the situation.
      • On-site: 5–6 people.
      • Online: 3–4 people.

  4. ❓ When should specifications be discussed and updated?

    • 🅰️ During mob sessions.
      • However, minor formatting and consistency fixes can be done later.
        • In such cases, final review via pull requests is necessary.

  5. ❓ How can multiple screens be shared?

    • 🅰️ Choose software that supports it.
      • Zoom allows it.
      • Alternatively, use a large screen for sharing.
      • 4K resolution is recommended.

Notes & Impressions​

  1. More screens enhance sharing capabilities.
    • A conference tool supporting multiple screen sharing is ideal.
  2. Using VSCode Live Share enables source sharing beyond just screen sharing.
  3. One driver, all others are navigators.
    • The driver should focus on typing rather than thinking.
  4. Meetings with clients should involve the whole team.
    • This reduces miscommunication and improves immediate response accuracy.
  5. Driver Responsibilities:
    • Speak while typing.
    • Clearly express intent when coding.
  6. Navigator Responsibilities:
    • Support if the driver pauses or hesitates.
    • Ensure alignment on aspects not covered in the design.

Tips​

  1. Share the driver's screen to avoid miscommunication.
  2. Verbalize your thoughts clearly.
  3. Don't hesitate to say "I don't know."
  4. Maintain professionalism: Be humble, respectful, and trustful.
  5. Celebrate small wins!
    • This is crucial for motivation.
  6. For online sessions, performance matters.
    • Especially the network environment.

Benefits​

  1. Newcomers can observe and learn the practices of experienced members.
  2. Handovers become more effective beyond just documented procedures.
  3. Team members can gauge each other's skills firsthand.

Challenges​

  1. Reserved individuals may find it difficult to speak up.
    • Other navigators should encourage and involve them.
  2. It can be exhausting.
    • Balance mob time, breaks, and reflections properly.
  3. Not everything requires mobbing.
    • Repetitive tasks or experienced teams can work individually as needed.