BONUS: Collaboration between Product Owners and Developers with the Digital Product School

Every 4 months, about 8 teams comprised of University students, other students, and partner-company employees start working on a new product idea at the Digital Product School (DPS).

These teams become their own mini-startups, and work to develop, and sell their products in a 3-month accelerated program. They experience hands-on what it is to work in a start-up and to go from a fuzzy idea (the problem space) to a product they can sell in a very short period of time. 

This learn-by-doing program helps companies educate their employees in rapid product development methods, and helps students get hands-on experience with product development in a very short period of time. 

The most common problems teams face in DPS

The teams that join and complete DPS usually have the same problems all other teams face, but because of the accelerated time-frame, and because the DPS team has seen more than 10 batches already, the problems are obvious! And we can learn a lot from those problems when it comes to the more normal product development we participate in. 

The first challenge teams face is that they have a hard time locking down the problem they want to solve. As it happens, they want to solve too many problems, which is a common affliction of many teams and leads to confused and confusing products. 

The DPS team expected that it would be hard to convince developers to work with users and do user research. However, it turns out developers actually embrace that work, and the biggest problem is getting the Product Managers (PMs) to make decisions. PMs tend to expect that the “process” will ensure they have a good outcome, and that leads to having a hard time making decisions. 

In this segment, we talk about how to help PMs make decisions and the transformation that happens when PMs are faced with the need to make decisions. 

The biggest problem in the Developer-PM collaboration

In such an accelerated program (3 months from idea to product), it is natural that the pressure is high at some point. PM’s work needs to include facilitating and motivating the teamwork. Why are we doing certain decisions? What’s the goal of a certain user test? And many more questions come up during the work. 

This brings one of the biggest problems in the Developer-PM collaboration: the motivation of the team when under pressure. In this segment, we also talk about the most common anti-patterns developers and PMs fall into when under pressure. There are also some great insights for Scrum Masters about team building and coping with pressure!

Enabling good Developer-PM collaboration

One of the usual sticking points in the Developer-PM collaboration is the fact that these people speak different languages. Many Scrum Masters also experience that when they see PMs and developers fight about estimations, for example. 

At DPS, special attention is put into helping PMs understand what developers do and vice-versa. From explaining and using tools that developers use, to helping developers understand Story Maps and other PM tools, the way the DPS team helps developers and PM’s collaborate is especially about helping each other and learning each other’s job and responsibilities.

Why Product Manager and not Product Owner?

At DPS, the team decided early on to call the role of the product person the Product Manager, and not the Product Owner. Why did they do that? 

In this segment, we explore a question that most companies adopting Scrum will need to struggle with: what to call the product roles. 

The DPS team shares how the idea of “product” is owned by the whole team, and that the product manager role is much more than looking at the backlog or defining priorities, it’s about being responsible for user experience, business, and technology!

This emphasizes the idea of the DPS program: product development is a team sport! 

Resources for rapid product development

At the end of the episode, we talk about what resources DPS suggests teams to study, and we list the following books: 

About Digital Product School

DPS is an accelerated product development program in Munich that helps students from University and employees in partner companies experience hands-on what it is to work in a startup. In 3 months they go from idea to a product, and some ideas are brought back to the companies for further development. 

About the DPS team

Michi / Michael Stockerl is director of DPS and has worked as a software engineer with several teams in different setups. Before that, he gathered experience in smaller Startups in Munich and Germany’s biggest Q&A platform.

 

Steffen is a trained journalist, who slipped into product management through Content Management and e-commerce. He worked with Amazon and Haymarket media, did several hundred user interviews and tests, witnessed dozens of teams at DPS, a Digital Product School of the Technical University of Munich in Germany.

Bela is a Software Engineer at DPS. She helps teams with various software and hardware engineering tasks. She was previously also a participant at DPS. 

BONUS: The Agile Wire hosts interview Vasco Duarte on #NoEstimates – Jeff Maleski & Jeff Bubolz

This is a BONUS episode on the topic of #NoEstimates. The Agile Wire podcast hosts Jeff Bubolz and Jeff Maleski interview Vasco Duarte.

Some of you might have heard about #NoEstimates, and want to know more, and for others, it might be the first time you hear about it. Either way, in this episode we talk about the origins of #NoEstimates and why you may want to consider it when helping your teams. 

This is a shared episode with a fellow Agile podcast The Agile Wire, where hosts Jeff Maleski and Jeff Bubolz interview Agile practitioners. Both Jeff Maleski and Jeff Bubolz have been guests here on the Scrum Master Toolbox podcast.

About Jeff Bubolz and Jeff Maleski

Jeff Bubolz is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.

You can link with Jeff Bubolz on LinkedIn and connect with Jeff Bubolz on Twitter.

Jeff Maleski is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.

You can link with Jeff Maleski on LinkedIn.

BONUS: Business Agility, what it is and how to achieve it with Evan Leybourn

What is Business Agility? In a time where it seems that every company wants to adopt Agile, there’s also the dark side of Agile: the belief that it only affects “people in the IT department”. That could not be further from the truth.

In this episode, we have Evan Leybourn sharing what Business Agility is about, and why it matters for your organization.

The origins of Business Agility

Continue reading BONUS: Business Agility, what it is and how to achieve it with Evan Leybourn

BONUS: Does Agile play well in Leadership teams in organizations? – Diana Larsen and Jutta Eckstein

Diana and I were kicking around a few topics for this episode, and we ended up selecting “Agile and Leadership, friends or foes?” The idea is to talk about how Agile and Leadership play together (or not)

In this episode, we talk with Diana Larsen and Jutta Eckstein about what problems Leaders try to fix with Agile, what challenges they have when they try to adopt Agile, and we will do this with the focus on the Scrum Master role, and what they can do by working with the leaders of the organizations they work within.

Let’s start by defining some of the major challenges we see happening out there.

The 3 biggest challenges on how Agile plays (or not) with Leadership

Some of the challenges we mention in this episode are not new. You are probably familiar with many of them. We talk about how Agile requires us to think about leadership as a distributed responsibility that team members need to take on, which is itself a major challenge for Scrum Masters as they help their teams understand what that means in practice. 

We also discuss how important it is to understand that leadership is not simply a “role”, but also something we need to earn, including Scrum Masters.

Finally, we talk about the important role that leaders play for the teams they work with. Specifically in setting the direction that helps the teams adopt quicker processes like Hypothesis-Driven-Development, for example.

How Scrum Masters can cope with these challenges

We then discuss how Scrum Masters can understand, and learn to cope with these challenges. Not surprisingly, Agile Retrospectives come up as a critical tool for Scrum Masters to use when working with teams and their leaders. 

Regarding collaboration with leaders, we discuss how Scrum Masters can help teams focus on the right goals, which need to be defined in cooperation with leaders in the organization.

But there’s a second tool we discuss that complements perfectly the work we do with the retrospectives and helps the teams and leaders understand where they can contribute the most: visualization as a way to establish a shared context.

Do Scrum Masters really need to protect the team from their leaders? 

Stop me if you have heard this one before. Way back when I was taught that Scrum Masters need to protect the team from interference. Although it made sense to me at the time, with the passing of time, and after collecting more than a decade of experience, I have come to value a different approach. 

In this segment, we talk about the need (or not) to protect the team from Leadership interference. 

The goal, of course, is to generate a real collaboration between the team and the leaders in the organization.

The key resources on leadership and Scrum by Diana Larsen, Jutta Eckstein and Vasco Duarte

Given that leadership, and the collaboration between teams and leaders is a critical topic for Scrum Masters, we discuss some of the resources (books, podcasts, articles) we’ve found useful and informative on how to tackle that collaboration. 

Here are the resources we mention: 

 

How about you? What have been your major challenges when working with leaders in your organization? Leave a comment below and share the tools/books/podcasts you’ve found useful. 

About Diana Larsen and Jutta Eckstein

Diana Larsen co-founded and collaborates in leadership of Agile Fluency™ Project. Diana co-authored the books Agile Retrospectives: Making Good Teams Great; Liftoff: Start and Sustain Successful Agile Teams; Five Rules for Accelerated Learning; and the seminal “Agile Fluency Model: A Brief Guide to Success with Agile” article.

You can link with Diana Larsen on LinkedIn and connect with Diana Larsen on Twitter

 

Jutta Eckstein works as an independent coach & consultant. 

As a developer, she started with XP in 97/98, started scaling agile in 2001 (and published about that in 2004), and am now Jutta focuses on company-wide agility.

You can link with Jutta Eckstein on LinkedIn and connect with Jutta Eckstein on Twitter

You can learn more at Jutta Eckstein’s website, and check out Jutta’s books on Amazon and LeanPub.

Jutta’s Agile Bossanova book is available here.

The value that Agile coaching and Scrum Masters bring to your organization – Q&A with Jeff Campbell

Jeff is the author of Actionable Agile tools (available on Amazon, and direct from the author at bit.ly/aatbook). He joins us on this series of Q&A shows to answer questions you’ve submitted. You can submit your questions via our survey (short, about 2 min to fill-in) or by tweeting us @scrumpodcast with #agilejeff.

In this episode, we talk about the importance of technical excellence and how to help teams adopt that mindset.

How to explain the need for Agile coaching and Scrum Masters

Continue reading The value that Agile coaching and Scrum Masters bring to your organization – Q&A with Jeff Campbell

How to build trust with clients and stakeholders while getting what you deserve for your work: a story about trust

This is a guest blog post by Jacopo Romei. Author of Extreme Contracts, a book about how to build trust, and deliver value without traditional contracts.

How to build trust with clients and stakeholders while getting what you deserve for your work: a story about trust

Over the last ten years, I’ve experienced the direct impact of lack of trust in vendor-buyer and even colleague-colleague relationships. I’ve come to find that it is the main reason why collaborations in knowledge work fail.

I’ve tried to fix that in my own work as an independent consultant and when working with other colleagues. That’s why I ended up experimenting with a new type of agreements which are optimized for trust building. This experimentation resulted in a set of principles that I call Extreme Contracts. Now, all my customers and I use this approach to shape our collaboration and they have started using Extreme Contracts also with their customers.

Continue reading How to build trust with clients and stakeholders while getting what you deserve for your work: a story about trust

BONUS: Tim Herbig on Lateral Leadership a critical skill for Scrum Masters and Product Owners

Tim was faced with a problem. How to be a leader without any formal power. All Scrum Masters and Product Owners who have felt the responsibility, but not any “line authority” have faced the same problem. You need to help move the project along, but you can’t tell people what to do!

In this episode we explore the concept of Lateral Leadership how it can help you as a Scrum Master or Product Owner.

Tim Herbig is the author of Lateral Leadership a recent book published by Sense and Respond Press.

Continue reading BONUS: Tim Herbig on Lateral Leadership a critical skill for Scrum Masters and Product Owners

BONUS: Geoff Watts on what makes a great Scrum Master, the key challenges to Scrum adoption and much more about Agile

There are quite a few books out there about the Scrum Master job. However, the classic that many refer to over and over again here on the podcast is Scrum Mastery by Geoff Watts.

In the description of the publisher writes: “Scrum coach Geoff Watts has identified patterns that separate a good Scrum Master from a great one”.

As a podcast for Scrum Masters, we wanted to have Geoff on, to share the key insights in the book, but also what he learned since the book was first published in 2013.

But, before we go into those new lessons learned, let’s quickly review some of the key insights from the book

The key insights from Scrum Mastery, the book

Read on for the detailed show notes and all the links…

Continue reading BONUS: Geoff Watts on what makes a great Scrum Master, the key challenges to Scrum adoption and much more about Agile

BIG LAUNCH: The @scrumpodcast Coach Your Product Owner e-course v2.0

Helping our Product Owners is a key part of the job a Scrum Master has.

Product Owners, as Antti Tevanlinna puts it, are responsible for making value explicit! (a great episode, by the way!)

So, I’ve been working for 1 year to put this e-course together.

I’ve coached Product Owners (check the video below). I’ve released some modules to collect feedback, and finally, I’ve asked what makes it hard to coach your Product Owner.

All of that to make this e-course available to you! The Coach Your Product Owner e-course v2.0 is now available.

You can check it out here.

Read on for details and a surprise! 🙂

Continue reading BIG LAUNCH: The @scrumpodcast Coach Your Product Owner e-course v2.0

How Agile and Lean saved a hospital from bankruptcy! Twice!

All of us working with Agile and Scrum are used to the (sometimes) large transformations that these approaches can have at work. But it is not everyday we see the impact, the amazing impact, it can have on other types of work. How about this: Marcus Hammarberg, walks into a hospital and the hospital is about the crumble. Literally! The roof has collapsed, there’s dripping water and buckets everywhere and the second floor is overrun with debris. But that is not where the problems end…

A few months later, and using Kanban, Agile and Lean ideas the hospital is saved. But how did that happen?

Marcus explains his story, and the amazing transformation in his latest book: The Bungsu (now available for pre-order at Amazon), and we have a short video to explain the main points of the story right here.

Click on to see the video, and sign-up to get the first chapter of the book.

Continue reading How Agile and Lean saved a hospital from bankruptcy! Twice!