The developers you work with know that poor names are one of the most difficult impediments they experience. The names that aren't useless are actively misleading. What you may not know is that bad names also account for 30% of the cost of your stories and 20% of your bugs. Fix the names and you will go faster.

Most people try to come up with great names, but this rarely works because to do it well, a developer is juggling seven decisions at once. It turns out that to name a piece of code well requires design thinking at the same time as detailed cognition. Our brains cannot do this, so it overloads and then a bad name is born.

Arlo Belshee (20 years of programming experience) and Marian Willeke (15 years of instructional design experience) have combined forces to bring you a mobbing workshop simulation that gives YOU the tools to facilitate your development team through tiny habit shifts that will decrease story time by 30% immediately and decrease bugs by 20% over six months.

Attend this workshop to learn how you can reduce your developers' frustration while getting more features!


Outline/Structure of the Workshop

This workshop is a Train the Trainer motif focused on non-coders. We lead them through simulation how they can set up the mobbing workshop for their development teams, teach them the terminology through metaphors on what matters for them to know, and give them a facilitator's guide to follow to ensure a successful experience.

10m - discuss why this matters so much
20m - facilitate strategic planning to ensure success and overcome imposter syndrome
60m - simulation of mobbing workshop flow ****
10m - update plan based on exposure to workshop
20m - questions

**** The workshop is a simulation of Arlo representing the mobbing team with real code and doing real refactoring in-situ. My role as a non-coder is to walk through the facilitator's guide that they also have and can take notes and "facilitate" the workshop. Going through all the habits in a simulated manner takes about 60m. We skip the videos because they are targeted to the developers in lieu of the non-coder's lack of knowledge. However, we take that time in the simulation to summarize the concepts that the videos cover and help them (audience) understand what the devs need to know and how to facilitate the conversation to get to the video.

We have performed this workshop at Agile 2019 with a high degree of success and empowerment for product owners and scrummasters. A couple testimonials we received as a result include:

  • I feel like I can talk to them [devs] now!
  • I've facilitated mob programming before, but I never had these good questions!

Learning Outcome

  • Understand the business implications and benefits of refactoring
  • Develop a plan for facilitating the workshop to your development team
  • Discover the challenges and subsequent waste that developers face with naming conventions
  • Discover a path to reduce developer frustration while increasing business outcomes

Target Audience

Product owners, scrum masters, tech leads, front line managers

Prerequisites for Attendees

  • Familiarity with basic agile processes (improvement cycles, iterations, etc)
  • Experience with facilitation
schedule Submitted 1 year ago