Member-only story
Five Ways Bad Product Owners Screw Up Scrum Teams
When Product Owners miss the mark, the entire organization suffers from pointless results.
Originally published in GoRetro
Many things can ruin Scrum teams, but one aspect stands out for me. A Bad Product Owner will obliterate the success chances of any team.
I’m not exaggerating because I’m a product person by heart. I’m talking from painful experiences and recognition of my f*ck ups.
Look at the other Scrum accountabilities. An amateur Scrum Master will drastically reduce the Scrum adoption, but the team still has success chances. The same would go for inexperienced developers. They will slow the team down but not impede them from growing.
A bad Product Owner will destroy any chance of standing out.

Wearing the Product Owner’s hat is tough. You can’t ignore the complexities of living up to a solid Product Owner’s responsibilities. Yet, it’s easy to take some wrong steps and put you and success in opposite directions. Let me share with you five common mistakes bad Product Owners make.