Steve Tendon shares what you need after Scrum

Steve has studied highly productive teams, and he shares with us some stories as well as what is necessary after Scrum is there. He also shares a tool that may be critical in our work as Scrum Masters.

In this episode we refer to the TameFlow community where he shares his ideas about high performing teams.

About Steve Tendon

Steve Tendon popularised the Theory of constraints in some of the agile community and he is also the Creator of the TameFlow systems thinking approach which nurtures breakthrough performance innovation. This system is described in the book with the same name: Tame the Flow

You can link with Steve Tendon on LinkedIn and connect with Steve Tendon on Twitter.

Paru Madhavan asks us to focus on the team, to understand the system

Start with the team! Paru asks us to consider the team when looking at the overall system. We can use the Squad Health Check (also the Atlassian version) survey or some other similar tool to understand how the system is influencing the performance of the team. As we go through the questions, then consider how the external (to the team) factors may be influencing the team. Listen in to learn how Paru uses these tools and other tools to help understand the system around the team.

About Paru Madhavan

Paru works as Scrum Master across two squads at OFX. She’s worked in Agile teams and in various roles such as Business Analyst, Product Owner and Scrum Master since 2011. To her, Agile and software development just go hand in hand!

You can link with Paru Madhavan on LinkedIn and connect with Paru Madhavan on Twitter.

Paru Madhavan on the personal and team aspects of success for Scrum Masters

When we start our journey as Scrum Masters, many of us start from the perspective that the team is the focus of our work, and the product is the outcome a job well done. However, we also need to consider our own development as people and Scrum Masters. Paru shares her thoughts on both the team and the personal aspects of our successful journey as Scrum Masters.

About Paru Madhavan

Paru works as Scrum Master across two squads at OFX. She’s worked in Agile teams and in various roles such as Business Analyst, Product Owner and Scrum Master since 2011. To her, Agile and software development just go hand in hand!

You can link with Paru Madhavan on LinkedIn and connect with Paru Madhavan on Twitter.

Paru Madhavan on the journey from Scrum to Kanban (and back)

Many teams go through a crisis in their Scrum adoption. They don’t feel good about the ceremonies, it’s hard to keep the discipline of regular meetings to review the backlog, keeping the stories small enough to deliver value in a sprint, schedule meetings that fit the stakeholders, etc. Scrum is full of disciplined approaches to specific knowledge work problems. So this team decided to go to Kanban. Listen in to learn what happened to the team, and how Paru helped the team find its way again.

About Paru Madhavan

Paru works as Scrum Master across two squads at OFX. She’s worked in Agile teams and in various roles such as Business Analyst, Product Owner and Scrum Master since 2011. To her, Agile and software development just go hand in hand!

You can link with Paru Madhavan on LinkedIn and connect with Paru Madhavan on Twitter.

Paru Madhavan and the impossible case of the ever-changing priorities

It’s hard enough to deliver on time when the backlog is fairly static, but what happens when the backlog is ever changing. The CTO drops-in every other day to change the priorities, all decisions are made on a spur of the moment, the team does not have all the necessary skills to deliver (i.e. not cross-functional)? Listen in as Paru explains how she lived through such a situation.

About Paru Madhavan

Paru works as Scrum Master across two squads at OFX. She’s worked in Agile teams and in various roles such as Business Analyst, Product Owner and Scrum Master since 2011. To her, Agile and software development just go hand in hand!

You can link with Paru Madhavan on LinkedIn and connect with Paru Madhavan on Twitter.

Paru Madhavan on how to handle spikes to avoid delivery problems

Paru shares with us a story that illustrates one of the biggest risks with spikes: the confidence that we know how to develop something. How can we then help a team that believes they found “the solution” to take advantage and learn from spikes without getting hung up on a particular solution?

About Paru Madhavan

Paru works as Scrum Master across two squads at OFX. She’s worked in Agile teams and in various roles such as Business Analyst, Product Owner and Scrum Master since 2011. To her, Agile and software development just go hand in hand!

You can link with Paru Madhavan on LinkedIn and connect with Paru Madhavan on Twitter.

BONUS: Gunther Verheyen introduces Reversify, the future of Scrum

In this Bonus episode, Gunther introduces an approach that he has developed over the years, to help companies that are struggling with Scrum in particular or Agile in general. But before that, we have a very interactive conversation about some key questions for Scrum Masters and Agile Coaches.

The biggest struggles in Agile Adoption

We start by reviewing some of the biggest and most common struggles that companies face when adopting Agile. In this question, we not only review the most common obstacles, but we also tackle the true origin of Scrum and Agile. Why it is there, and what are the promises of this way of working that get forgotten in many of the Agile adoptions in the world. Scrum, specifically was created to improve the quality of the workplaces where it is used. But is that idea followed in practice?

The biggest obstacles to successful Scrum Adoption

Many organizations start from the point of view that Scrum is a way for teams to work. That is far from the truth, according to Gunther. Scrum is a whole organization way of working, with the PO (product Owner) role being an example of a role that transcends the team focus and works with the whole organization to help create an understanding of value that ultimately gets translated into the team’s work backlog. Gunther points to the biggest silo of them all, as an example of how we misunderstand Scrum: the silo between “business” and IT.

Removing the obstacles to successful Scrum Adoption

How do we remove obstacles to the successful adoption of Scrum? With a specific approach to Scrum adoption that Gunther shares with us. This is an approach that he has developed over the years and reflects the patterns of successful adoption he’s seen. He calls this approach the “Scrum Zone”.

Reversify your organization with Scrum, after you’ve solved the major obstacles

Once the major obstacles to adoption are overcome, we then need to understand where to take Scrum in our organizations to make it a core productive engine for our businesses. This is what Gunther calls “Reversify, re-imagining your organization”: make it a productive engine, a core of value production that aligns the whole organization. This is an approach that Gunther has been developing over the last few years and shares with us in this unique BONUS episode about the future of Scrum.

References

During this episode we mention several resources. Here’s a list for your reference.

 

About Gunther Verheyen

Gunther left consulting in 2013 to partner with Ken Schwaber, Scrum co-creator, at Scrum.org. He represented Ken and Scrum.org in Europe. Gunther left Scrum.org in 2016 to continue his journey of Scrum as an independent Scrum Caretaker.

He calls himself a connector, writer, speaker, humaniser. Gunther assists, serves, advices teams, individuals and executives.

Gunther believes that Scrum – the most applied software development framework – will not only increase the value that software delivers to organizations but is also a way to re-humanise the workplace for people. Gunther likes to inspire individuals, teams, departments, and organizations to realize their potential.

Beyond Scrum, Gunther is all about his family, life, books, and music. He communicates in Dutch and in English. Gunther is co-creator to Agility Path and the Nexus framework for Scaled Professional Scrum.

You can link with Gunther Verheyen on LinkedIn and connect with Gunther Verheyen on Twitter.

Khaja Mohiuddin how the bigger purpose of the organization influences the team

The purpose of the organization is a big influencer on the team’s performance. But once that obstacle is surpassed we need to help the team take ownership of their own development, and Khaja shares a technique that can help the team find its place and flow within the organization.

About Khaja Mohiuddin
An accomplished and fluent communicator with strong investigation, problem-solving and decision-making skills. Managing the work from initial request through estimation, approval, requirements, build and implementation.

You can link with Khaja Mohiuddin on LinkedIn.

Khaja Mohiuddin shares 4 steps every Scrum Master can follow to help teams succeed

A lot has been said about what it means for a Scrum Master to succeed. Khaja takes a different approach in this episode and shares with us how we can help our teams succeed. He shares 4 steps he has successfully used in this own practice when taking on new teams, or reaching a tough spot with an existing team.

About Khaja Mohiuddin
An accomplished and fluent communicator with strong investigation, problem-solving and decision-making skills. Managing the work from initial request through estimation, approval, requirements, build and implementation.

You can link with Khaja Mohiuddin on LinkedIn.

Khaja Mohiuddin on how reducing the size of the change increases the pace of the change

There are many reasons why teams don’t like or even resist change. One of those reasons is the perceived difficulty or size of the change. It’s ok to take on big challenges, but sometimes they just feel impossible. Khaja shares with us how he approached such a situation where a team felt that Agile itself was a change large enough that it was scary. How do we help teams like that? Listen in.

About Khaja Mohiuddin
An accomplished and fluent communicator with strong investigation, problem-solving and decision-making skills. Managing the work from initial request through estimation, approval, requirements, build and implementation.

You can link with Khaja Mohiuddin on LinkedIn.