This post is about learnings and reflections of our mob programming teams from an enterprise perspective. Not so much about the benefits for the team itself, but the impact on the organisation and its processes, the obstacles that may appear, and the ways to navigate around those obstacles. Continue reading
In April 2010, the Icelandic volcano Eyjafjallajökull’s dramatic eruption caused an ash cloud that kept the travel industry in its vicious hands for several days. The closure of the european airspace resulted in 100,000 cancelled flights…
Seven years later, one morning in March, two meetings take place.
Meeting 1: Replanning of Enterprise Project X
Project X has been running for more than two years and has reached a serious state. The implementation involves 10+ teams and an external vendor. Not only are the budget, plans and scope dark red from a traditional PMO RAG status view, but energy and motivation are drained, teams are exhausted, and project management is lost. Continue reading
Just like many developers like pair programming, I like to pair in my role as a change agent. And when you think about it, most of the benefits from pair programming are not related to programming specifically.
Having observed our mob programming teams for sometime I’d like to highlight one benefit: business risk management.
Many of our development teams have a 24/7 online business to support. And about 70% of our total business happens online. Imagine the risk associated with not having the right knowledge available instantly when needed.
Every year when summer and holiday planning comes up we have the same challenge: how to secure operations when most people are away? And even if knowledge sharing was good there were always the special details that only one or two people knew.
Well, this summer this is not an issue. Everyone in the team knows every piece of their product. Everyone has been involved in every change, all discussions, all deploys and knows every flaw there is to know.
One of the highest business risks mitigated.