In Holidaycheck’s Poznań IT department we work in teams that consist of frontend & backend developers. We pay a lot of attention to knowledge sharing within a team in order to have a common understanding of our architecture and why we’ve chosen one solution over another . For a long time we’ve had well balanced sprints, meaning that we had a few frontend and backend tasks in each sprint. Recently however, due to our business strategy and migration process of our platform, more and more tasks have became frontend focused.
We didn’t want our backend devs to get bored! We wanted to use the potential of the whole team, which meant involving backend devs in frontend tasks. We started looking for solutions that can be helpful in learning new technology stack. One of the things that came to mind was pair programing, which is a great idea for sharing knowledge, but… our scrum master proposed to try MOB programming… We thought: “Why not!? We are an agile team, so why not to try something different and learn !?” 😉
MOB programming in a nutshell, is a scaled up version of Pair programming, with more than two developers. In our case it was four: two frontend and two backend guys. We’ve prepared one of our conference rooms to be the headquarters of our MOB programming session. We used a big TV as an external monitor – just to feel more comfortable and not to squeeze four people in front of a tiny laptop screen for hours 🙂 Second laptop was used for research, to not disturb the main flow of coding.
We’ve picked one frontend story, which was not very complex, but great for learning the basics. At the beginning of our MOB session, backend part of our team had a feeling that the story is just a piece of cake … but it wasn’t. Backend guys haven’t had any experience with our current frontend stack and didn’t have a clue about how complex and tricky the story might be. After we’ve discussed how we would implement the story, we were ready to code! Development process looked a little bit different from pair programming. One of the developers was a “driver”, sat in front of the laptop and owned the keyboard. He was coding what was discussed and agreed on by everyone. The session revolved around frontend guys suggesting how the story should be done, which was then being discussed by everyone. From time to time, we also had a discussion regarding more general programming ideas like testing approach etc. The MOB session was divided into short iterations (15-20 min) in which each of us became the driver, which allowed previous driver to focus on research and discussion.
- sharing knowledge
- new angle of looking at solutions that we are using on daily basis
- rise of team spirit and collaboration
- backend guys started to like coding on frontend stack
- the session slowed down the progress of product features in the current sprint, but that was expected and accounted for, as we believe it will enable us to be faster in future
- frontend guys would love to do a similar session with a backend story 🙂
- a whole day is too long to develop in that style
- MOB approach shouldn’t be abused! 🙂
In summary, although we had certain reservations before we started, MOB programming turned out to be a really great experience for us! We think we will be using it in future, as a mean of fast learning and knowledge sharing… Maybe frontend guys will learn & love Scala? 🙂 Time will tell… 🙂