Mob programming is a software development model where the whole team works on the same thing, at the same time, in the same space, and at the same computer. This is a whole team approach to doing all the work the team does - including coding, designing, testing, and working with the customer (partner, product owner, user, everyone!).
We have expanded the team nature of all the work we do - not just planning, retrospectives, and a daily stand-up or other meeting. This is an evolutionary step beyond the pair programming, face-to-face communication, team alignment, collaboration and self organising team concepts of the agile approach to software development.
I'll share how we've been using this as our daily practice to super-charge our development efforts and deliver high value software for almost 5 years. We'll see what it looks like, the benefits, and how to do it yourself. In our workplace we mob program all day, every day, but we'll also explore how to use all of the concepts and practices (and get the benefits) of mob programming in your own company even if you can't do it all the time.
Woody Zuill has been programming computers for 30+ years, and is an independent agile coach and trainer.
His team at Hunter Industries originated the Mob Programming approach to teamwork in software development, and Woody is considered one of the founders of the #NoEstimatesdiscussion on Twitter.
Over the last 15+ years he has worked as an agile coach, application development manager, trainer and extreme programmer.
He believes that code must be simple, clean and maintainable so that we can realise the agile promise of responding to change, and that we must constantly ""inspect and adapt"".
Woody has a passion for tackling code that is hard to maintain and cleaning, refactoring and bringing it back into a manageable state.
To buy tickets to see this fantastic talk, and many others like it head over to our ticket page.
Need help planning which sessions to attend? We've provided a breakdown of our various session types below.
A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of Agile and Lean practices. Case studies and experience reports include some discussion of lessons learned and an indication of how novel the work is.
Participants learn a new approach, tool or technology through using it to solve one or more practical exercises. Any software/hardware requirements are disclosed in the session description.
A session focused around some specific tool, technique or issue. Primarily led by the speaker, tutorials usually include some elements of interactivity or individual / group exercise.
An in-depth working session on a specific topic. May include paper presentations.