In the beginning I would like to stress that this is not yet another article about Minimum Viable Product (MVP)
mechanics. For theory and examples of its use in practice, please refer to the great article by Andrzej Winnicki. What made me share my thoughts on MVP is what
I consider a prerequisite to start working with this method. Moreover, I also recognised this prerequisite as the
biggest obstacle which is stopping many enthusiasts from fully understanding it.
The aim of this blog post is to summarise an experiment that took place between two
scrum teams at the end of 2014 and to share our lessons learned. Have you ever worked
in close cooperation with another team? Of course you have. But how close is close?
Have you ever wondered what happens when you go one step further than cooperation and
you actually mix two teams, stir or even shake? During that time we discovered a lot about team dynamics,
sources of inner responsibility that is essential for any team to make commitments and what are the biggest obstacles
on the way towards self-organisation. So, without further ado, let the story begin…
Scrum Master with 4+ years of professional experience, passionate about Agile product development, team dynamics and its evolution and coaching. At Allegro since 2013, currently working with teams from Finance and Payment Departments.