Six Dangerous Pitfalls Scrum Teams Often Face
Originally published in GoRetro
There’s no such thing as one size fits all. My whole life, I heard that sentence in different contexts, but I wonder if Scrum or any other Agile frameworks strive for this approach of one size fits all. I’ve worked for several companies, from startups to massive corporations, from South America to Europe. I’ve been in many different segments, the public sector, automobile, online shopping, and the list goes on.
What astounds me is not the flexibility of the Scrum framework, but the common pitfalls I faced anywhere I’ve been
When I look back, there are some things I wish I knew, yet nobody told me. I had to figure out my mistakes on my own. Allow me to share the six common pitfalls I recognized with most Scrum teams. Hopefully, you can avoid them and create value faster with your teams.
The following traps come mainly from a Product Owner’s perspective, but might be beneficial for any team member to help the team escape from such traps.
#1 Bullshit Management
A massive trap is starting a Scrum without having anyone with relevant product management experience on board. The result is frequently terrible. Instead of…
