Overcoming Common Product Backlog Management Traps — David Pereira at the 54. Hands-on Agile

•

0 likes•112 views

Stefan Wolpers

Business

David Pereira, 10th of October, 2023
Overcoming Common Backlog Traps

Company
Marketing
Customer Service
Management
Operations
Product Team

Company
Marketing
Customer Service
Leadership
Operations
Product Team
WHAT’S THE
PROBLEM HERE?

The Backlog Trap transforms
teams into feature factories

Product Backlog Check
menti.com
1420 9858

Keeping an extensive Product Backlog to tell
stakeholders their requests are registered instead
of removing items unrelated to your current goals
#1
d-pereira.com

Gathering requirements from stakeholders to
solve their wants instead of establishing
relationships to deliver on end-users needs
#2
d-pereira.com

Fear of removing outdated backlog items force
you to work too much on the backlog and too
little on creating value
#3
d-pereira.com

When everything can go in, your backlog
becomes no more than a 6-year-old wish list
#4
d-pereira.com

Creating solutions without knowing
the problems they aim to solve
#5
d-pereira.com

d-pereira.com
The longer the backlog,
the less agile you can be
Common Backlog Traps

d-pereira.com
Extensive Backlog Once in, never out
6-year-old wish list
Common Backlog Traps
Solutions without
problem
understanding
Focus on pleasing
stakeholders over
satisfying users

Mismanaged product backlogs
transform Scrum into Waterscrumfall
d-pereira.com

Cleaning your Product Backlog is
essential to create value

Old promises
New promises
Nice to have
Old
New
Lean Backlog
No
Yes
Traditional Backlog Management Lean Backlog Management

Don’t increase the backlog size
Increase the trash bin size

First you’ve got to clean
your Product Backlog. Then,
you’ve got to keep it shiny

Product Manager
Requests
Requests
Requests
Requests
No
Yes
Saying no to distractions enable focus
Every yes you give,
you gain a new responsibility
David Pereira

January April July
New requests, old items down,
new items up
New requests, old items down,
new items up
With an extensive backlog,
everyone wants to run away
David Pereira

January April July
New learnings in
Old items out
New learnings in
Old items out
Inspect and adapt, remove distractions.
Focus on goals; not plans
David Pereira

Backlog
Item
Age
Keep the Product Backlog clean.
Backlog items age like milk, not like wine
d-pereira.com

Encourage teams to step
back, re#ect, and
challenge the status quo

Product Backlog Health Check
d-pereira.com
Backlog items
live forever
Due Date
Backlog items live no longer
than 3 months
A mixed of everything
Goal Related
Most of the items
relate to a common goal
Unstructured
Organization
Simple and easy to understand
Focus on writing
requirements
Focus on learning
Focus on adapting to
learnings
More than a hundred
items
Lean Backlog
No more than a couple
of dozens of items

You’ve got a choice to make:
Bow to the status quo and get stuck
Challenge the status quo and have a
chance of a better tomorrow

Untrapping Product Teams
Supercharging your product knowledge to rock the world
Join 13K+ professionals to get weekly insights dpereira.substack.com
David Pereira
Simplifying Product Management
contact@d-pereira.com
d-pereira.com

What's hot

Kanban vs Scrum: What's the difference, and which should you use?

Arun Kumar

Backlog refinement is not a Scrum event, but instead is an ongoing activity during the Sprint required to decompose, describe, estimate, and order backlog items in the Product Backlog. This material is divided into two sections. The first section reviews the basics of backlog refinement, covering various options for conducting the activity. The second section covers tips for maintaining a healthy backlog and potential anti-patterns. This material was presented at Agile New England in July and August 2022 as "101" introduction and "202" advanced sessions.

Backlog Refinement 101 & 202

David Hanson

Agile Performance Metrics

ACM

Building a Company-Wide Growth Culture: SaaStr Annual 2016

Sean Ellis

Agile Estimation Techniques

Mikalai Alimenkou

Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...

Vidas Vasiliauskas

Agile Development Methodology: Best Practices and Use Cases

Celerity

Introduction agile scrum methodology

Amit Verma

Agile scrum fundamentals

Deniz Gungor

Agile Scrum software methodology

Abdullah Raza

Cost of delay and prioritization techniques

Murali Mohan Narayanabhatla

Leading stakeholders and development teams is notoriously challenging for product people: They lack the power to tell the individuals what to do, but need their support to progress the product. To make things worse, stakeholders come from different departments and often have different perspectives and interests, which leads to disagreements and conflicts. This talk shares my tips for dealing with difficult stakeholders, constructively resolving conflict, and creating value together.

Dealing with Difficult Stakeholders: Tips for Product People

Roman Pichler

Agile Retrospectives

Allison Pollard

When any organization plans to move to Agile methodology, it needs to plan multiple initiatives for successful transition. One of the important initiative would be building an Agile Center of Excellence, a team which would support for consistency of Agile implementation across the organization. The Agile CoE we built worked on multiple aspects such as: Defining organization-wide Agile methodology, tailoring it as per organization environment if required. Build knowledge of Agile across the organization. Supporting the team members with any ongoing queries. Support in building required Tools and Templates required implementing Agile. Assessing Agile implementation of different projects, identifying any gaps or improvement areas. This session covered practical experience of how we built a successful Center of Excellence, which become a big enabler for successful Agile transformation.

Agile Center of Excellence : Presented by Rahul Sudame

oGuild .

Scrum retrospective

Priyanka Rana

Have you ever been in a prioritization discussion where the only priorities are High, Higher, and Highest? Or tried using MoSCoW to prioritize user stories only to find that 80% of the cards are 'Must Have'? In this tutorial, we introduce a gamut of different prioritization methods, ranging from simple techniques like stacked ranking or MoSCoW that classify items along a single dimension to multi-dimensional techniques like priority quadrants, Story Maps, and Innovation Games®. We cover pruning feature trees, spending fake currency, and using visual metaphors, while truly identifying what the most important stuff really is. This was most recently presented at the Agile India 2013 conference in Bangalore.

Prioritization Techniques for Agile Teams

Tarang Baxi

Modern Agile - Joshua Kerievsky

AgileSparks

Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation. Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world! “It's better to be roughly right, than precisely wrong!” ~ John Maynard Keyenes The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck! PROBLEMS WITH TIME-BASED ESTIMATES -Teams spend too much time trying to get it right -Lack of confidence/experience can lead to people being either optimistic or pessimistic -Timeline you are estimating may be too far in the future -Due to long timeline, there are too many risks, unknowns, changes or dependencies! WHY USE RELATIVE ESTIMATION? -Allows a quick comparison of stories in the backlog -Allows you to select a predictable volume of work to do in a sprint -Uses a simple arbitrary scale -Allows PO to make trade-offs and take on the most valuable stories next ESTIMATION TIPS -Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile. -The team estimates the story, not management nor the customer. -Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues. -Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes. -Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready. -Only pull into your sprint, stories that are refined and estimated. -Break down stories that are large, into smaller slivers of value to optimize your flow. -Don’t sweat it if you get it wrong, teams often do early on but improve over time.

User Story Sizing using Agile Relative Estimation

Alex Kanaan, SPC5, CSP, ACC, ATF

How to facilitate product backlog refinement sessions

LuxoftAgilePractice

Session Abstract: Agile framework is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. It’s a set of values and principles that help teams respond to unpredictability through incremental, iterative work cadences and continuous feedback. Scrum is the most popular methodology under the Agile umbrella. Scrum emphasizes empirical feedback, team self-management, and striving to build shippable product increments within short iterations. Kanban is another popular flavor of Agile that focuses on visualizing and managing the flow of work, in order to balance demand with available capacity and remove bottlenecks. Learning Objectives: > Gain a broad understanding of the Agile framework > Discover Scrum and Kanban, the two most widely used Agile methodologies, and see how they can be used in construction industry > Find out how Scrum and Kanban can be combined to have the best of both worlds (Scrumban)

Introduction to Agile - Scrum, Kanban, and everything in between

Pravin Kumar Singh, PMP, PSM

What's hot (20)

Kanban vs Scrum: What's the difference, and which should you use?

Backlog Refinement 101 & 202

Agile Performance Metrics

Building a Company-Wide Growth Culture: SaaStr Annual 2016

Agile Estimation Techniques

Scrumban - applying agile and lean practices for daily uncertainty by Vidas V...

Agile Development Methodology: Best Practices and Use Cases

Introduction agile scrum methodology

Agile scrum fundamentals

Agile Scrum software methodology

Cost of delay and prioritization techniques

Dealing with Difficult Stakeholders: Tips for Product People

Agile Retrospectives

Agile Center of Excellence : Presented by Rahul Sudame

Scrum retrospective

Prioritization Techniques for Agile Teams

Modern Agile - Joshua Kerievsky

User Story Sizing using Agile Relative Estimation

How to facilitate product backlog refinement sessions

Introduction to Agile - Scrum, Kanban, and everything in between

Similar to Overcoming Common Product Backlog Management Traps — David Pereira at the 54. Hands-on Agile

Sales insider issue 12

MoatazBellah Magdi

What Is Team Demand, And Why Should I Care?

Receptive

Backlog Blunders

Joe Combs

Lean Software Development: Validated Learning

Òscar Vilaplana

Ryan's Lean Startup 3-Hour Workshop

Ryan D. Hatch

9 Lessons for New Product Managers

HubSpot

Taking In-House Product to Market

Dinker Charak

In this marketing webinar you will learn why businesses should be adapting their brand strategy during COVID-19. You will learn what a brand strategy is and how changing consumer needs, emotions and competitive environments are impacting your brand. We will review real life examples of what leading and local brands are doing to adapt their own strategies and take-away five strategies you can implement in your own brand storytelling to remain relevant during this challenging time of unprecedented change.

Adapting Your Brand Strategy During COVID-19

Andrea Martin

Content itself is the biggest obstacle keeping marketers from taking better advantage of SlideShare — that is, the obstacle of coming up with content ideas for SlideShare presentations. After all, once you decide on a concept and structure for a presentation, finishing the presentation usually moves forward quite nicely. The hard part is coming up with the initial idea. To help you get over that hurdle, here are 12 easy-to-create SlideShare ideas — enough for a year’s worth of monthly presentations. These ideas are followed by tips for putting them to work, and for leveraging your completed SlideShare presentations.

12 Months of Content Marketing Ideas for SlideShare

Content Marketing Institute

Friends With Jill Overview

Ashwin Tiwari

You know how to build great software. The real question is - // What software do customers actually want to buy? // Do you have a new product / business idea? Learn how to validate new product concepts. Join our Precon 3 Hour Master Class: * You will learn the latest best practices for taking new products to market * Live B2C Customer Interview * Hands-on Collaboration with other attendees Learn how to transform product ideas into a successful business. Learn how to interview customers. Learn how to create business models using a test-driven approach. Learn how to avoid the top reasons for startup failure. Learn how to run experiments to validate your assumptions and navigate the uncertainty of new products. Meet some awesome people & expand your new product chops. WARNING: New products are hard, exciting, and may become highly addictive. Only come if you want to make a dent in the world.

2016.08.THAT Conference - GROWING NEW PRODUCTS - VALIDATING YOUR NEW PRODUCT ...

Ryan D. Hatch

How do you define a successful business? Earl R. Davis

Earl R. Davis

Discover the crucial role design plays in your business's performance and success. This white paper explores the distinctions between good and poor design and delves into the intricacies of achieving exceptional design. We examine its influence on product, package, website, and direct-mail design, accompanied by insightful case studies that illustrate real-world applications. Learn how quality design can attract customers and boost sales, while poor design can have adverse effects on your business.

Unlocking Design's Impact on Business Success - A White Paper.pdf

printbenton

information need for paper Why Is This Important? Product development is the engine for making innovations—new ideas—come to life. This is at the heart of what businesses do. In fact, without an understanding of how to develop new ideas and turn them into products, businesses wouldn’t exist. The companies that have been around for decades, such as GE or Apple, continue to thrive because they know how to listen to customers, generate new ideas, and turn those ideas into products their customers love and—most importantly for the business—purchase. Companies who aren’t able to go through this process won’t have anything to sell that customers want. Those companies will lose their customers to competing businesses. Without customers, a company won’t be around for long. That’s a big risk for a business. Companies also need to know how well a product is doing in the market. Is it still new and exciting, and are sales growing? Are customers continuing to buy it, and have sales been steady over the last few months? Or do people seem to not want the product anymore, and are sales starting to fall? These phases are all natural parts of the product life cycle. It’s important for businesses to be able to recognize each of these phases. For example, if customers no longer want a particular product, a company can begin the process of creating a new, better product to replace the current one. Businesses need to know when and how to introduce these new products. QUICK QUESTION: Do you work for a company that consistently creates new and interesting products? Or have most of the products been around for a while? What companies come to mind that do a good job of introducing new products? How Does This Connect to the Other Parts of Business? Products and services are the backbone of a business. Companies exist because they have something valuable to offer their customers. Without that, a company has nothing to sell—and customers have nothing to buy. That, of course, means there is no money for the accountants and finance team to track and measure. Sure, a business can have a leadership team and strong management, but it will just be people in an office with nothing to sell. How will it compete with other businesses with a product? This is why we’re starting with product development. Throughout the rest of this course, you’ll learn how products are sold to customers, how those sales lead to profits and growth, and how strong teams can lead companies to do even more. But remember, all good businesses are built around a product or service that meets a need or addresses an opportunity. Now, let’s jump right into this week’s materials with an Explore Activity. STRAYER TALKS: PRODUCT DEVELOPMENT WITH ALIKAY NATURALS “Everything changes and nothing stands still.” — HERACLITUS, GREEK PHILOSOPHER THE IMPORTANCE OF CHANGE You may have heard it before: “The only constant is change.” This is especially true in business, where companies must constantly ...

information need for paperWhy Is This ImportantProduc.docx

lanagore871

Danny Maher

commercialisation

How to Build the Right Thing

Lokal

MVP - Minimum Viable Product

Barry Doctor

Innovation & Product Considerations

Ryan Frederick

Innovation & Product Considerations

AWH

What Sucks About Product Management by Salesforce Sr PM

Product School

Similar to Overcoming Common Product Backlog Management Traps — David Pereira at the 54. Hands-on Agile (20)

Sales insider issue 12

What Is Team Demand, And Why Should I Care?

Backlog Blunders

Lean Software Development: Validated Learning

Ryan's Lean Startup 3-Hour Workshop

9 Lessons for New Product Managers

Taking In-House Product to Market

Adapting Your Brand Strategy During COVID-19

12 Months of Content Marketing Ideas for SlideShare

Friends With Jill Overview

2016.08.THAT Conference - GROWING NEW PRODUCTS - VALIDATING YOUR NEW PRODUCT ...

How do you define a successful business? Earl R. Davis

Unlocking Design's Impact on Business Success - A White Paper.pdf

information need for paperWhy Is This ImportantProduc.docx

Danny Maher

How to Build the Right Thing

MVP - Minimum Viable Product

Innovation & Product Considerations

What Sucks About Product Management by Salesforce Sr PM

More from Stefan Wolpers

Your team is supposed to use an agile approach, such as Scrum. But you have a years-long backlog, your standups are individual status reports, and you’re still multitasking. You and your team members wish you had the chance to do great work, but this feels a lot like an “agile” death march. There’s a reason you feel that way. You’re using fake agility—a waterfall lifecycle masquerading as an agile approach. Worse, fake agility is the norm in our industry. Instead, you can assess your culture, project, and product risks to select a different approach. That will allow you to choose how to collaborate so you can iterate over features and when to deliver value. When you do, you are more likely to discover actual agility and an easier way to work. Now, there is light at the end of the tunnel; let's delve into Tackling Fake Agility with Johanna Rothman!

Tackling Fake Agility w/ Johanna Rothman

Stefan Wolpers

ABSTRACT Your team is supposed to use an agile approach, such as Scrum. But you have a years-long backlog, your standups are individual status reports, and you’re still multitasking. You and your team members wish you had the chance to do great work, but this feels a lot like an “agile” death march. There’s a reason you feel that way. You’re using fake agility—a waterfall lifecycle masquerading as an agile approach. Worse, fake agility is the norm in our industry. No one has to work that way. Instead, you can assess your culture, project, and product risks to select a different approach. That will allow you to choose how to collaborate so you can iterate over features and when to deliver value. When you do, you are more likely to discover actual agility and an easier way to work. LEARNING OBJECTIVES Have a clear understanding of the different lifecycles and when to use each. Be able to assess your project, product, and portfolio risks. Know how to customize a lifecycle based on the unique culture and requirements of the team. How to create shorter feedback loops in any lifecycle for product success. MEET JOHANNA “People know me as the “Pragmatic Manager.” I offer frank advice—often with a little humor—for your tough problems. I help leaders and managers see and do reasonable things that work. Equipped with that knowledge, you can decide how to adapt your product development, always focusing on the business outcomes you need. My philosophy is that people want to do a good job. They don't always know what they are supposed to do, nor how to do it.”

Hands-on Agile #59: “Agile” Does Not Work for You? Tackling Fake Agility w/ J...

Stefan Wolpers

Abstract: Humble Planning: How To Make Your Plans Suck Less In this talk, Maarten will introduce the concept of humble planning and why it's crucial for succeeding with an Agile way of working and building products of exceptional value. When faced with uncertainty, risk, and complexity, our natural response is to focus on what we know and to spend more time talking, analyzing, planning, and predicting. As a result, our plans become filled with speculation and rooted in our imagination. Our plans as an anchor stifle the ability to respond to changes. We become locked into plans that prevent collaboration, learning, and discovery. In this talk, Maarten will show why instead of starting with overconfident plans, we should start with humble plans: How can we encourage our teams to begin with humble plans and what do teams need to adapt their plans as they discover and learn what’s necessary while doing the work? The talk will cover concepts like friction, the three gaps model of Bungay, intent, intent-based leadership, humble planning, sprint goals, the fog of beforehand, and the fog of speculation. Meet Maarten Dalmijn Maarten Dalmijn is a consultant, speaker, and trainer at Dalmijn Consulting. He is the author of the book Driving Value with Sprint Goals. Maarten helps teams to beat the feature factory all over the world. Millions of practitioners have read his best-practice articles on Agile, Scrum, and Product Management. He specializes in helping companies to build empowered teams that can discover better ways of delivering value. Maarten is a frequent speaker at Fortune 500 companies and international industry conferences. He has worked with many award-winning start-ups and scale-ups. He is an ambassador and editor at Serious Scrum, the largest Scrum publication on Medium.

How To Make Your Plans Suck Less — Maarten Dalmijn at the 57th Hands-on Agile...

Stefan Wolpers

(1) Abstract: Designing Agile Ecosystems with Org Topologies™ Over the past decade, heavyweight methods like SAFe® have dominated the agile landscape, offering tools for “scaling agile.” Yet questions arise about their prescriptive nature and genuine agility. Framework-agnostic approaches like Team Topologies™ and unFix™ have recently emerged, offering more flexible, “buffet-style” organizational design choices. However, they demand a deep understanding of organizational design, systems thinking, and queuing theory to avoid pitfalls. Org Topologies™ bridges the gap between rigid frameworks and DIY methods by emphasizing ecosystems—interconnected organizational parts that exhibit specific behaviors. Co-creators Alexey Krivitsky and Roland Flemm will introduce a method to navigate and improve organizational ecosystems for agility. (2) Meet Alexey Krivitsky Alexey Krivitsky, a pioneer Scrum Master in Ukraine since 2005, is a CST, CEC, and organizational agility coach. He’s a notable conference producer and speaker and created the lego4scrum game. (3) Meet Roland Flemm Roland Flemm transitioned from a 20-year developer career to a Scrum Master in 2009, specializing in large-scale Scrum consultations from 2015. An active conference speaker, he created the Koos Coach comics and “Elements of Scrum” learning cards.

Designing Agile Ecosystems with Org Topologies™ — Hands-on Agile #55

Stefan Wolpers

How teams manage their Product Backlog often makes or breaks their value creation chances. Poor backlog management leads to a feature factory trap, while a mindful strategy enables the team to drive value steadily. Over the years, David has identified common traps teams often face and learned how to overcome them the hard way. Let David help you identify such challenges and help you overcome them, too. David is a passionate Product Leader with over ten years of product management experience. Over the last few years, he led many product teams in successful endeavors. His biggest fear is the comfort zone. His motto is the faster we learn, the faster we succeed. He has been working as a Product Leader. He’s focused on coaching teams to deliver the highest value for their customers. One of his hobbies is writing articles. He shares his ideas on Substack and loves learning from everyone. Join the Hands-on Agile Meetup here: https://www.meetup.com/hands-on-agile-berlin-chapter-meetup/

Overcoming Common Product Backlog Traps — Hands-on Agile 54 w/ David Pereira

Stefan Wolpers

“I’m going to tell you a story. I was coaching an agile coach who lamented that they weren’t connecting with their coaching client, in this case, a development manager. I asked them to share a typical coaching conversation, and they spoke about a series of questions they asked that essentially went unanswered—leaving them and the client quite frustrated. I asked them what other coaching techniques they had tried, and it boiled down to only coaching stances and only open-ended questions. I suggested they experiment with weaving some stories into their coaching conversations. Personal stories, lesson-learned stories, teaching stories, purpose or vision stories, and relationship or connection-building stories. I spoke to them about sharing their knowledge and wisdom with the client via story, not dominating the conversation but augmenting it, and using the story as a backdrop to their questions and explorations with the client. They later told me that this small change significantly impacted their coaching after a bit of practice. This talk is about bringing the power of Storytelling INTO your agile coaching and discovering the magic of the Story. Now, please share this story with others, and I hope to see you in the talk…”

Bob Galen: An Agile Coaches’ Guide to Storytelling — Hands-on-Agile #53

Stefan Wolpers

Engage the Agile Fluency® Model with Diana Larsen — Hands-on Agile #46

Stefan Wolpers

How can multiple teams work together on a single product? The common wisdom is to carefully align teams and responsibilities to create autonomous teams. But, invariably, this approach eventually runs into cross-team bottlenecks, challenges aligning responsibilities to teams, and difficulties creating cross-functional teams. Fluid Scaling Technology, or FAST, is an innovative new approach that solves these problems. It uses frequent team self-selection to prevent bottlenecks, share knowledge amongst teams, and ensure the right people are working on the right things. It’s simple and lightweight. During the 45th Hands-on Agile meetup, James Shore shared his experiences with scaling Agile: first with traditional approaches and, more recently, with FAST. Learn in about an hour what works, what doesn’t, and how you can try FAST in your organization.

James Shore: FAST: An Innovative Way to Scale — Hands-on Agile #45

Stefan Wolpers

My Top Ten of the Meanest Scrum Anti-Patterns — ScrumDayUkraine 2021

Stefan Wolpers

Hands-on Agile #19: The Successful Scrum Master

Stefan Wolpers

Scrum Master Career 2020 — Using Ecocycle Planning to Identify Opportunities

Stefan Wolpers

The 16th Hands-on Agile meetup continues exploring Liberating Structures for Scrum events. This time, we address the Sprint Review. Liberating Structures cover a set of easy to learn, yet powerful ways to collaborate as a team—even as a large team—, overcoming traditional communications approaches like presentations, managed discussions, or another disorganized brainstorming at which the loudest participants tend to prevail. Throughout the coming months, we will create exciting new ways how to improve classic Scrum events like the Daily Scrum, the Sprint Review, or the Sprint Retrospective. Moreover, we will use Liberating Structures for difficult challenges that agile coaches, Scrum Masters, and Product Owners face, for example, reviewing the existing product design process.

Liberating Structures for Scrum: The Sprint Review

Stefan Wolpers

The 15th Hands-on Agile meetup continues exploring Liberating Structures for Scrum events. This time, we address the Daily Scrum. Liberating Structures cover a set of easy to learn, yet powerful ways to collaborate as a team—even as a large team—, overcoming traditional communications approaches like presentations, managed discussions, or another disorganized brainstorming at which the loudest participants tend to prevail. Throughout the coming months, we will create exciting new ways how to improve classic Scrum events like the Daily Scrum, the Sprint Review, or the Sprint Retrospective. Moreover, we will use Liberating Structures for difficult challenges that agile coaches, Scrum Masters, and Product Owners face, for example, reviewing the existing product design process.

Liberating Structures for Scrum: The Daily Scrum

Stefan Wolpers

The twelveth Hands-on Agile meetup continues exploring Liberating Structures for Scrum events. Liberating Structures cover a set of easy to learn, yet powerful ways to collaborate as a team—even as a large team—, overcoming traditional communications approaches like presentations, managed discussions, or another disorganized brainstorming where the loudest participants tend to prevail. Throughout the coming months, we will create exciting new ways how to improve classic Scrum events like the Daily Scrum, the Sprint Review or the Sprint Retrospective. Moreover, we will use Liberating Structures for difficult challenges that agile coaches, Scrum Masters, and Product Owners face, for example, reviewing the existing product design process. This second meetup of the “Liberating Structures for Scrum” series will address the Sprint Retrospective.

Hands-on Agile: Liberating Structures for Scrum: The Sprint Retrospective

Stefan Wolpers

Sprint Retrospective Anti-Patterns — Hands-on Agile Webinar #10

Stefan Wolpers

Sprint Review Anti-Patterns — Hands-on Agile Webinar #9

Stefan Wolpers

Scrum Master Ant-Patterns — (Hands-on Agile Webinar #8)

Stefan Wolpers

Scrum Sprint Anti-Patterns (Hands-on Agile Webinar #7)

Stefan Wolpers

Hands-on Agile Webinar #6: Product Owner Anti-Patterns

Stefan Wolpers

The third Hands-on Agile webinar product addresses backlog anti-patterns — from out-dated and oversized tickets to the part-time proxy product owner and his or her idea repository. Learn more about the numerous product backlog anti-patterns that can manifest themselves when you try to create value for your customers and your organization. BLOG: https://age-of-product.com/webinar-product-backlog/ YOUTUBE: https://www.youtube.com/watch?v=fCE1PmtbGXQ

Hands-on Agile Webinar #3: Product Backlog Anti-Patterns

Stefan Wolpers

More from Stefan Wolpers (20)