BONUS: Allan Kelly and Vasco Duarte on #NoProjects and #NoEstimates the latest trends in the Agile community

This is an episode about #NoProjects, #NoEstimates and introduces a unique, and 1-time-only workshop by Allan and Vasco that will take place in August 21st, 2018 in Zurich, just before the ALE2018 Unconference. Check out this page about the #NoProjects and #NoEstimates Workshop to know more.

In the past few years a few new trends have emerged in the Agile community that have challenged some of the basic assumptions of how software should be delivered. The first one, #NoProjects is challenging the idea that software work is best managed as a project. As Allan puts it in this episode: “Successful software does not end. It continues. And projects are for temporary endeavours, that have a known start and fixed end. That’s now how software is developed today.”

With that start to the episode you can expect that many unconventional (and inconvenient?) ideas will be shared in this podcast focused on the latest trends in how to manage software development.

Read more… Continue reading BONUS: Allan Kelly and Vasco Duarte on #NoProjects and #NoEstimates the latest trends in the Agile community

Kyle Aretae on how Scrum Masters can help teams address conflict without a blow-up

For Kyle, Agile solves 2 problems. One is the building of software in a better, more sustainable manner. The other is to create a functioning organization, which will become a better place to work. In this episode, Kyle also explains how a simple technique can help the team address behavior that negatively affects the team without ever making that a personal conflict.

Featured Book of the Week: Darwin’s Dangerous Idea by Daniel C. Dennet

Kyle was struck by the book Darwin’s Dangerous Idea by Daniel C. Dennet. It helped him understand the enormous difference between plannable systems and evolutionary systems. That helped him understand the impact that Agile could have on organizations. During his research after reading that book he also came across Interactual Ritual Chains by Randall Collins, which helped him understand the role of (Scrum) ceremonies in the development of the team, and ultimately led him to write one of his own books: Ceremony: A Profound New Method for Achieving Successful and Sustainable Change by Kyle Aretae and Thomas Meloche

About Kyle Aretae

Kyle has been programming since ’81. Teaching since ’91. Practicing Agile (Extreme Programming – XP) since 2000. Kyle is always interested first in better ways to understand things and systems. Especially interested in Complex (CAS/VUCA) Systems like building software or the economy at large.

You can find Kyle Areate at DiamondAgile.com, or link with Kyle Areate on LinkedIn.

Kyle Aretae on what Scrum Masters must focus on, beyond the teams

Kyle’s background as a developer has informed his view of how teams can achieve the level of collaboration needed to be successful in an Agile environment. Having read Kent Beck’s Extreme Programming Explained book, he started to work with developers, helping them improve their ways of working. But that wasn’t enough. In this episode, we explore what is beyond the team that can make or break an Agile transition.

About Kyle Aretae

Kyle has been programming since ’81. Teaching since ’91. Practicing Agile (Extreme Programming – XP) since 2000. Kyle is always interested first in better ways to understand things and systems. Especially interested in Complex (CAS/VUCA) Systems like building software or the economy at large.

You can find Kyle Areate at DiamondAgile.com, or link with Kyle Areate on LinkedIn.

Faye Thompson Reminds us: People are NOT Resources!

There’s the temptation that people are as easily replaceable as parts in a machine. But is that the case? And if you answer “no”, what does that mean for you as a Scrum Master? In this episode we explore the many reasons why treating people as “resources” causes problems in the long run.

In this episode, we refer to the book Age of Agile by Steve Denning.

About Faye Thompson

Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.

You can link with Faye Thompson on LinkedIn and connect with Faye Thompson on Twitter.

Faye Thompson on how the Scrum Master must focus on stakeholder happiness as a success measure

When we discuss the success of a Scrum Master, happiness is a word that often comes up. Is the customer happy? Is the team happy? Are some of the questions we must ask ourselves, and in this episode, Faye reviews how we can ask, collect the answer for and use those to help our work as Scrum Masters.

Featured Retrospective Format for the Week: Single Word Retrospective

In the Single Word Retrospective, the team reflects on how one word impacts their way of working. In this episode, Faye shares one concrete example of what that could look like in practice.

About Faye Thompson

Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.

You can link with Faye Thompson on LinkedIn and connect with Faye Thompson on Twitter.

Faye Thompson on how Agile Retrospectives are the core of the change process

There are many tools out there to support a change process. So many in fact, that we often forget the humble Retrospective. The most important tool in our Scrum Master toolbox: reflect and adjust, inspect and adapt – the core cycle of change.

In this episode, we explore how the Agile Retrospective can become the engine of self-driven team change.

About Faye Thompson

Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.

You can link with Faye Thompson on LinkedIn and connect with Faye Thompson on Twitter.

Faye Thompson on how a poor Product Owner can destroy the team’s ability to deliver

Many things can fail when we work with teams. But one critical anti-pattern that leads to problems is the lack of a good Product Owner. In this episode, we explore what are the consequences for our teams of having a Product Owner that is unable to filter input from many stakeholders or even to politely say “No!”. Listen in to learn about the many anti-patterns that can come from a poor Product Owner.

Featured Book of the Week: any book by Gerry Weinberg

Faye has followed the work of Gerry Weinberg and recommends that to all Scrum Masters. She mentions several of Gerry Weinberg’s books in this episode, for example: The Secrets of Consulting, or An Introduction to General Systems Theory. For Faye, Gerry’s work is an example of what Scrum Masters work is about: being humane.

About Faye Thompson

Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.

You can link with Faye Thompson on LinkedIn and connect with Faye Thompson on Twitter.

Faye Thompson on how to be a humane Scrum Master

“We don’t leave our human-selves at the door once we come into work!” – this is how Faye starts this episode. The question is: as a Scrum Master, what does it mean for me? Faye’s journey to the Scrum Master role gives us some insights into the wide-spread consequences of that phrase. It also links directly to the story of failure that Faye has to share with us. It is a story of how a team member started bullying other team members. Listen in to learn to detect bullying signs early on.

About Faye Thompson

Faye calls herself a Scrum Master and agile coach, and she enjoys working with teams to solve cool business problems while not being jerks to one another.

You can link with Faye Thompson on LinkedIn and connect with Faye Thompson on Twitter.

Ilya Bibik on why Scrum Masters need to go beyond the cultural stereotypes

Ilya has lived in 3 different countries, and currently lives in Canada where the IT industry is a melting pot of many cultures. That has taught Ilya a lesson: cultures are stereotypes that don’t really apply to single individuals. Being aware of those stereotypes is useful, but Ilya suggests we go deeper.

Listen in to learn how to go beyond the cultural stereotype and learn about the individuals you work with.

In this episode we refer to Ilya Bibik’s book: How to Kill the Scrum Monster.

About Ilya Bibik

Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.

You can link with Ilya Bibik on LinkedIn and connect with Ilya Bibik on Twitter.

Ilya Bibik: How Scrum Masters can detect when the team is ready to be self-sufficient

As we evolve our practice, we help the team be self-sufficient. Over time, the team will be able to handle most of the Scrum process itself. But how do we detect when the team is ready for that final step in their maturity? In this episode we talk about the signs Scrum Masters can look for to detect when the team is mature enough to be self-sufficient.

In this episode we refer to Ilya Bibik’s book: How to Kill the Scrum Monster.

Featured Retrospective Format for the Week: The Flexible Retro

When we focus on having the Retrospective as a “ceremony”, there’s a risk that it becomes just that: a ritual that has little impact. Ilya’s approach is different. In this episode we describes a very simple format, and how you can make retrospectives fun again. The Flexible Retrospective format.

About Ilya Bibik

Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.

You can link with Ilya Bibik on LinkedIn and connect with Ilya Bibik on Twitter.

Ilya Bibik on why Scrum Masters must focus on “one change at a time”

When teams start with Scrum, there’s the temptation to define and implement many changes at the same time. After all, there’s a lot of new practices to take in. However, Ilya’s suggestion is different. Listen in to learn about the idea of “one change at a time”, and how you may be able to apply it in your context.

In this episode we refer to Ilya Bibik’s book: How to Kill the Scrum Monster.

About Ilya Bibik

Ilya has about 16 years experience in software development and more than 7 years experience in the Scrum Master role. On top of Software engineering, Ilya has also a background as a school teacher and military service that helps him with his Scrum Master role. Recently Ilya published a book “How to Kill the scrum Monster” that he wished he had read 8 years ago.

You can link with Ilya Bibik on LinkedIn and connect with Ilya Bibik on Twitter.