TL; DR: Scrum Developer Anti-Patterns
After covering the anti-patterns of the Scrum Master, the Product Owner, and the stakeholders, this article addresses Scrum Developer anti-patterns, covering all Scrum Events and the Product Backlog artifact. Continue reading and learn more about what to look out for if you want to support your teammates who build the Increment.
TL; DR: Scrum Stakeholder Anti-Patterns
Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization.
TL; DR: Product Waste, Little’s Law & Forecasts — Food for Agile Thought #344
Welcome to the 344th edition of the Food for Agile Thought newsletter, shared with 35,342 peers. This week, we delve into the patterns of product waste resulting from an ‘organizational and conceptual gap’ between product and engineering teams on the one side and sales and marketing teams on the other side. Also, we outline how to support your teams emotionally in challenging times, and we visualize the mental model of developers as systems thinkers, from inner and outer loops to flow states to context switching. Moreover, we reflect on those who ‘dodge gatekeepers and dance around policies, doing whatever it takes to get the job done.’
Then, we provide insight into Stripe’s product strategy, resulting in a ‘microcosm of product-led, developer-centric growth.’ Moreover, we guide the reader from JTBD to user-centered design to the CCVC framework, and we listen to Chad McAllister interviewing Mike Mace on how to get customer insights quickly to counter demands from your resident HiPPO or a pushy sales team.
Also, we show how the application of Little’s Law can support your team’s forecast quality, and, finally, we address the widespread belief that Kanban is nothing more than some columns on a board and a handful of cards to push around, resulting in highly complex boards of little value.
TL; DR: 15 Sprint Review Anti-Patterns
Are we still on track to accomplish the Product Goal? Moreover, how did the previous Sprint contribute to our Scrum team’s mission? Answering these questions and adapting the Product Backlog in a collaborative effort of the Scrum Team with internal and external stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns.
TL; DR: Sprint Retrospective Anti-Patterns
What event could better embody Scrum’s principle of empiricism than the Sprint Retrospective? I assume all peers agree that even the simplest form of a Retrospective—if only held regularly—is far more helpful than having a fancy one once in a while, not to mention having none. Moreover, I am convinced there is always room for improvement; just avoid dogmatism. Hence, learn more about 21 common Sprint Retrospective anti-patterns that will hold back your Scrum team.
TL; DR: Scrum Master Anti-Patterns
No other role in Scrum can contribute to mediocre outcomes like the Product Owner—garbage in, garbage out. Therefore, the following list of some of the most common Product Owner anti-patterns might be a starting point to reflect on the role; maybe, there is room for improvement?
If you recognize some anti-patterns in your daily work, why don’t you ask the rest of the Scrum Team for support? For example, run a Retrospective with teammates and stakeholders on how the team is doing regarding figuring out what is worth building.