Elena Popretinskaya on what we can learn from Modern Agile about forming a Scrum team

Teams change. It’s a fact. Some team members join, sometimes two teams get merged. That’s the story we talk about in this episode. Elena was facing a challenge. A new team was formed from two previous teams. How to help the team form?

Elena tried several things, including forming the team around a common goal they called “a mission”.

However, forming a team is not an easy task. What have you tried? Listen in to learn what Elena tried, failed, and then learned from this story.

In this episode we talk about Modern Agile, a movement to highlight some aspects of Agile that often get forgotten.

About Elena Popretinskaya

Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂

You can link with Elena Popretinskaya on LinkedIn and connect with Elena Popretinskaya on Twitter.

Catrine Björkegren on how to react to conflict in a Scrum team

As we work with several teams, it is impossible to avoid working with team members that just don’t have good chemistry. As Scrum Masters, we should be ready for when that happens! In this episode, we talk about a particular incompatibility between team members and reflect on how to handle this type of conflicts.

About Catrine Björkegren

Agile coach and scrum master, Catrine has worked with agile for a decade in various areas like education, nuclear waste, government agencies, pharmaceutical and at the Royal Swedish Opera.

She believes that co-location is the key to building teams and that leadership is the key to successful agile transformation.

You can link with Catrine Björkegren on LinkedIn and connect with Catrine Björkegren on Twitter.

Kristopher Stice-Hall: how to keep meeting-inflation in check for remote Scrum teams

When working with remote teams we must be aware that the number of meetings can easily balloon up because the team does not meet in the corridor. As Scrum Master, we must help remote teams find workarounds for the calendar-driven, meeting-inflated anti-pattern for remote teams.

In this episode, we discuss how a Scrum Master can help a team find the right balance between meetings and ad-hoc interaction even when remote.

About Kristopher Stice-Hall

Is the co-owner of Digital Maelstrom, a consultancy specializing in custom software, DevOps, managed cloud services, and information security. He has been doing Scrum Master work for over 10 years. He has worked with fortune 500 companies to companies less than 15 people. He also has been doing software development for 17 years.

You can link with Kristopher Stice-Hall on LinkedIn and connect with Kristopher Stice-Hall on Twitter.

Varun Maheshwari: common mistakes Scrum Masters do when getting started with Scrum

Scrum is a relatively small framework for teams to adopt. Certainly much smaller than some of the Agile at scale frameworks. However, even small frameworks can take a while to adopt. In this episode, we reflect on some of the most common mistakes Scrum Masters make when helping teams adopt Scrum.

About Varun Maheshwari

Varun is a Scrum Master and agile practitioner in Australia. He believes in “being agile” rather than “doing agile”. For him, Agile frameworks are not the goal, but rather “Delighting customers, Zero Defects, Quick ROI, Better team work, Excellent Quality & Shortest ‘Time to Market’” are some of the possible goals.

You can link with Varun Maheshwari on LinkedIn.

Elena Astilleros on why every Scrum team is a different challenge for Scrum Masters

After a successful assignment as a Scrum Master, it is possible we think we’ve got the role down to a T. However, reality between teams is so different that even great Scrum Masters can struggle when moving from one team to another. We share one such story, and what principles and practices we can take as Scrum Masters to focus our work on the new team.

About Elena Astilleros

Elena coaches people who hate wasting their time with badly run agile ceremonies, meetings or projects. She gives them tools to get more out of their time while sprinkling in a little enthusiasm and cheerleading. You can find some of her tools in the forthcoming book Invisible Leader.

You can link with Elena Astilleros on LinkedIn and connect with Elena Astilleros on Twitter.

Eduardo Ribeiro: on the perils of applying Scrum by the book

Scrum Masters naturally want their teams to apply Scrum “the right way”, but there are risks with that approach. As Scrum Masters, we must be able to detect when a team is getting frustrated by our actions, no matter how well-intentioned they might be. In this episode, we talk about a team that started to feel frustrated by Eddy’s approach and how he reacted to that. Helping the team get back to the positive adoption of Scrum

About Eduardo Ribeiro

Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.

He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.

You can link with Eduardo Ribeiro on LinkedIn and connect with Eduardo Ribeiro on Twitter.

Nedeljko Damnjanovic on the Scrum Master journey from “doer” to “enabler”

Many Scrum Masters have a background in other roles within their teams. Some were developers, others Project Managers, others Testers, etc.

Many of those roles are “doer” roles. Roles that focus more on execution and less on helping others execute.

As Scrum Masters, we must be able to transition from “doer” to “enabler”, and Nedeljko shares his journey with us.

Click to learn more about how you can help your PO

About Nedeljko Damnjanovic

Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.

You can link with Nedeljko Damnjanovic on LinkedIn.

You can find Nedeljko and the rest of the team at VivifyScrum on twitter.

Henrique Centieiro and the tool-Scrum anti-pattern

Joining a team, it is good to see that they have their tools in order. They can follow-up progress, track what is missing and even leave notes for each other in the items they add to the tool. The problem is when the tool starts to take over the team, instead of the team owning the tool. In this episode, we talk about the tool-Scrum anti-pattern, when the team focuses more on the tool than the things it should enable: communication, collaboration, progress assessment, and metrics.

In this episode we refer to the book Lean Startup by Eric Ries and the work on Hypothesis Driven Development by Barry O’Reilly.

About Henrique Centieiro

Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.

You can link with Henrique Centieiro on LinkedIn.

Ajeet Singh: the pitfalls when Scrum Masters overly rely on the team

It is one of the mantras in the podcast: “take it to the team”. That mantra helps Scrum Masters focus on helping teams grow and learn from their mistakes. However, there’s a pitfall hiding in that mantra, and that’s when we rely too much on the team. As Scrum Masters we are also the accountability partners for the team. When we don’t pay attention, bad things can happen. In this episode, we discuss the pitfalls of relying too much on the team, and how to avoid this anti-pattern.

About Ajeet Singh

Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.

You can link with Ajeet Singh on LinkedIn and connect with Ajeet Singh on Twitter.

Tilman Rumland on Anti-Patterns of Scrum adoption

Scrum adoption, just like any other process or framework, is not free from troubles. Especially when organizations are already in the middle of a problematic situation.

In this episode, we review several anti-patterns of Scrum adoption, including hierarchic struggles, abusing the Scrum roles to make them just another set of titles, the extreme attention to the Product Owner role, and many others.

About Tilman Rumland

Tilman Rumland is an agile coach, expert speaker, and productivity enthusiast. He just released his new workshop series: “getting shit done that really matters to you”. As a scrum master, he implemented agile structures to agrilution, a small scale vertical farming startup, ranked on the Forbes TOP 100 innovative German Startups. (www.agrilution.com)