The Product Owner Summit call for sessions is live. Submit your session now!

I want to submit a session!

Sarah O’Brien on the line manager anti-pattern in Scrum

Scrum teams are supposed to be fully responsible for their work, and autonomous in the way of working. However, in many organizations line managers are still the ones yielding the power over teams, and even assign work directly to team members. This is one of the system conditions we must face and struggle with as Scrum Masters. In this episode we discuss how to interact with line managers, so that the Scrum team can really be responsible and autonomous as Scrum suggests.

About Sarah O’Brien

Sarah is passionate about helping teams work together to bring value to their work lives. She has worked in the Scrum Master role for the past 6 years after transitioning out of waterfall as a senior software engineer. Her (not so) secret goal is to help people bring agile practices home.

You can link with Sarah O’Brien on LinkedIn.

Jella Eifler on how different questions can radically change how you plan software projects

The planning system, i.e. all the planning approaches, and techniques we use, can often create a set of non-negotiable needs that teams need to fulfill. Starting with up-front planning! If our planning system requires estimates for every possible feature in the roadmap, then the teams will inevitably need to estimate a lot of work that will eventually not be done at all! However, if our planning system is based on “value” instead, then the teams are asked different questions. Jella asks: “What if you would ask “is this worth doing?” instead of how “how much does this cost?”?” What kind of changes to your planning system would that change bring?

About Jella Eifler

Jella has a background in linguistics (totally non-tech) and calls herself “agile native” (having never worked any other way, at least in software development). She works as a Scrum Master since 2014 at Qudosoft in Berlin. She has worked with both colocated as well as distributed teams.

You can link with Jella Eifler on LinkedIn and connect with Jella Eifler on Twitter.

Natalie Warnert on how observation can help you uncover the system

Natalie explains her approach to understanding and visualizing the system conditions that affect the teams she works with:

  1. Start by asking “how are the tools, practices and policies affecting the team’s I work with?”
  2. Then take a pen and draw the links between the different observations, do this with the whole team. Expect to hear many different perspectives, and help the team make sense of those different views.
  3. Use also metrics, but not just one. Look at several metrics and ask people to look beyond a single metric, and beyond the metrics. What do these metrics tell us?
  4. Identify possible underlying conditions that affect the team.

Always keep in mind, that this process will be different for every team you work with, each team is different.

About Natalie Warnert

As a developer turned Agile coach, Natalie Warnert understands and embraces what it takes to build great products. Natalie focuses teams on embracing Agile values to build the right product and build the product right. Natalie is currently coaching the Cart/Checkout teams for Best Buy Dotcom and recently earned her Master of Arts degree in Organizational Leadership and Strategic Management.
You can link with Natalie Warnert on LinkedIn, connect with Natalie Warnert on Twitter, read her blog at nataliewarnert.com, and visit her project page Women in Agile.

Gil Zilberfeld on the importance of collecting information to understand the systems conditions

Understanding the system we work within is a detailed and painstaking process of collecting and processing information. There are many questions we must ask as we collect that information. Gil shares with us the questions he asks to collect the right information about the system, and map the system conditions that affect the team.
In this episode we discuss Theory of Constraints, a body of knowledge that every Scrum Master should be aware of.

About Gil Zilberfeld

For over 20 years, Gil has developed, tested, managed and designed software products. He’s gone through failures and successes, in different types of projects and companies.
He has trained and coached developers how to write tests for their untestable code. He has worked with testers on complex applications and with very tight deadlines. He’s helped release products that fit customer needs, by testing the waters, and getting their feedback integrated. He has implemented agile, kanban and lean principles and adapted them to fit teams better.
You can link up with Gil Zilberfeld on LinkedIn, or find Gil Zilberfeld on Twitter.
Gil is writing a book on Unit Testing. Check it out.

Daniel Nielsen explains how to detect system conditions that affect your team

How can we detect the system conditions that affect our teams? Daniel has a method, that he explains in this episode. This includes writing down keywords you listen during the day, and looking for patterns in those keywords. Daniel also suggests that you look at the Agile Fluency model to look for indicators that your team is evolving, or not.

Special call to all Dubai agilists: Daniel is relocating to Dubai and is looking to connect to local agilists. If you fit the bill, then reach out to him on twitter: Daniel Nielsen on Twitter.

About Daniel Nielsen

Daniel is a developer turned Scrum Master turned Agile Coach, with an increasing focus on the coach part. Over the last 10+ years, his interest in how teams work and how we interact as individuals has only grown. He has worked in both small and large companies and tried to cope with the complexities in both worlds.
You can reach out to Daniel Nielsen on Twitter, and link with Daniel Nielsen on LinkedIn.
You can also read his blog in Danish at QED.dk

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