🚀 I help Scrum Masters, Product Owners and Product Managers Grow w/ Books, Classes, Courses, and Community. 📖 Author of the ”Scrum Anti-Patterns Guide;” 🏅Trainer at Scrum.org ⬇️ Book a 1-on-1 to discuss opportunities!
Your team’s success depends on the #ProductBacklog — don’t kill it! Hence, avoiding rookie mistakes is the first step! Consider applying Charlie Munger to Scrum. #Inversion How do you maximize the utility of your Product Backlog? 👇 Please share your expertise via the comments! Useful? Like / Follow / Repost
Ahh the backlog Stefan Wolpers Where hopes and dreams go to die 🫠
7 is most prevalent across. The complete Quarter is booked ahead in advance and teams give their "commitments". Let's not do that. I am not about the completeness of PBIs but rather the full blown list in the backlog.
In the last 12 years I struggled with all these anti-patterns... The hardest to brake were related to the size of the backlog, because most POs or teams love to have everything there, no matter how old or still relevant those items are.
If anyone in my network is looking for Refinement Anti-patterns, check this out! Stefan Wolpers if a master in detecting and listing anti-patterns in product development.
👉 You have not yet enrolled in the free email course on Scrum anti-patterns? Don’t miss out; hundreds already did: https://www.linkedin.com/pulse/new-scrum-anti-patterns-guide-free-email-course-stefan-wolpers-swjef/
Robert Navarette
1mo
5, 6, and 8 are bad habits that I always have to work with a new Scrum Team to break.
Renato Santos
1mo
Your schema is my mind! 😁 Well done!
Thanks Stefan keep sharing 👍
Very recognizable!
CEO | Helping leaders build great cultures through training & insights
1moSorry, I'm a bit confused by your post Stefan Wolpers. Are you in favor or against backlogs? You list out in your slides quite clearly a lot of the problems with them, which is why personally I advocate for no backlog except for things that you definitely know you'll be doing soon. Every backlog I've ever seen that has more than that always becomes a disaster area of too many items, no prioritization, and half baked ideas that sometimes repeat themselves. Now, you do need planning, and to think ahead, but it feels like that belongs somewhere else that doesn't clutter up the system your engineering team is using to track their current work.