Jesse Houwing: Scaled Scrum done wrong, and how to make it right!

Jesse was working on a large Scrum project. As he started observing the structure, he noticed something was off. This project had 17 teams, 17 backlogs, and 17 Product Owners. It was as if every team was in a little island. As he looked further, Jesse found that teams were optimizing the work for their own context and needs, at the same time destroying the ability of other teams to succeed. An example of how NOT to scale Scrum. 

We discuss what we can do when facing similar situations.

Featured Book of the Week: Code Complete by Steve McConnel

From Code Complete by Steve McConnel, Jesse learned some important lessons that helped him later on as a developer and as a Scrum Master. The aspects that Jesse highlights are the collaboration between developers, and how to work as a team when developing larger systems. 

In this segment, we also refer to Scrum, A Pocket Guide by Gunther Verheyen, who’s also been a guest on the podcast

About Jesse Houwing

Father of 2, husband of 1, Professional Scrum Trainer with, Steward of the Scaled Scrum curriculum there, gadgeteer and techy at heart. Lives in the middle of The Netherlands.

You can link with Jesse Houwing on LinkedIn and connect with Jesse Houwing on Twitter