Daniel Westermayr: The problem with cluttered backlogs and how to de-clutter them, coaching Product Owners

In this episode, Daniel Westermayr discusses his belief in the importance of the Scrum Master role in helping companies achieve their product goals. He shares his experience of encountering a cluttered backlog with items that were years old and how he cleaned it up, only to face complaints from someone in support. Daniel emphasizes the need for Scrum Masters to clarify why a large backlog is a problem, and why the company wants to keep all items. He also advises that Scrum Masters should understand what they stand for and constantly question why certain practices are being implemented. Finally, he suggests that, in order to avoid fears of losing important information, the older requirements can be stored in a safe location. Daniel also mentions an article on how to declutter product backlogs.

The inspiring story of how a failing hospital turned things around with Agile and Lean

Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story – How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

 

About Daniel Westermayr

Daniel is a Kanban Trainer with a knack for all things Lean and Theory of Constraints. He wants to help teams achieve and measure their continuous improvements.

You can link with Daniel Westermayr on LinkedIn.

Peter Janssens: The core value of the User Story format for Scrum teams and Product Owners

The Great Product Owner: The advantage of knowing Scrum in depth!

This Product Owner had a deep understanding of Agile and Scrum. This enabled him to focus on the core interaction with the team. Every week, he’d meet with the team for the Review and Planning meetings. Through that, he was able to guide the team, communicate the updated Vision for the product, and help the team select the stories for the Sprint without overcommitting. The knowledge the PO had of Scrum helped him focus on the right communication cadence, and topics with the team!

The Bad Product Owner: The core value of the User Story format for Scrum teams and Product Owners

Peter was a Product Owner for one of his first projects. The project was very well defined and prepared, and they decided to do it with Scrum. Peter then tried to split the requirements and work packages into stories on his own. However, he did not reformulate the requirements in a way that would convey the goal or purpose of each story, or the product itself to the team. This experience helped Peter understand why the User Story format is so important.

In this segment, we talk about Inspired, the book by Marty Cagan.

Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Peter Janssens

Peter built a long career in agile coaching and training, and worked in leadership positions leading a PO team, and recently became CTO in a SAAS product company. Peter loves all conversations on effectiveness of team decisions, but he quickly realized that being responsible is different from being a coach. As a leader there is the challenge of sticking to the same foundations when dealing with delivery pressure.

You can link with Peter Janssens on LinkedIn.

Robbie Ross: How to use the three amigos in Agile and Scrum to help teams handle complexity

Robbie was working with a large organization, and helping a team. But he quickly noticed that there was a wider, systemic impact for the change they were asked to do. When working with the team, he suggested that they consider the stories in a “3 amigos” session before Sprint Planning. When this new practice was adopted, it was clear that a simple change like adopting the “3 amigos session” had had a large impact on the team, and the surrounding environment. Listen in, to learn how the “3 amigos” session can help your team collaborate, and define better stories. Learn more about the 3 amigos meeting from Steve Thomas and the 3 amigos session strategy by George Dinwiddie, who were some of the first to propose the practice in the agile community.

About Robbie Ross

Robbie is an Agile Practice Manager at Jumar Technology with a passion for working with and empowering teams to foster an Agile environment at scale. He’s also a Certified Scrum Master, Kanban practitioner and Agile community member helping teams release their genuine potential to deliver value. Quite a career shift since completing a Sports Science degree at University.

You can link with Robbie Ross on LinkedIn and connect with Robbie Ross on Twitter.

Neil Killick how important it is to ask questions and how easy it is to forget that

We don’t ask questions often enough, and in this episode Neil explains why that is so important. Neil tells us a story of a project that started well, continued well, everything seemed to work well, until…
He discusses how one small detail derailed the whole project, and how to avoid that in the future.

About Neil Killick

scrum_master_toolbox_podcast_Andy_Deighton Neil has been a software professional for over 18 years, mostly as a developer, before moving to management. He spent the last 5 years being a passionate Agile, Lean and Scrum coach, trainer and practitioner. Neil cares deeply about creating enjoyable, authentic workplaces in which human potential can thrive.
You can connect with Neil Killick on twitter. Neil Killick’s blog.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works