Dominik Ehrenberg ask the right questions from yourself to define and measure success

Scrum Masters can achieve a successful outcome for their work if they are ready to ask the right questions from themselves. Whether we have a check-list of ask a Scrum Master colleague to serve as a sparring partner the key is to ask the right questions from ourselves!

About Dominik Ehrenberg

Dominik is a Scrum Master at Infineon Technologies AG in Germany. Agile practitioner since 2008, he started in the industry as a software developer in web development and later became a Scrum Master.
You can link with Dominik Ehrenberg on LinkedIn and connect with Dominik Ehrenberg on Twitter.

Dominik Ehrenberg on asking provoking questions to jumpstart change

Teams can get used to “the way things are around here” and fail to recognize that they are stuck in a rut. Asking the right questions can help teams get out of the rut and learn that they must learn to question even what “feels natural” in order to improve.

About Dominik Ehrenberg

Dominik is a Scrum Master at Infineon Technologies AG in Germany. Agile practitioner since 2008, he started in the industry as a software developer in web development and later became a Scrum Master.
You can link with Dominik Ehrenberg on LinkedIn and connect with Dominik Ehrenberg on Twitter.

Dominik Ehrenberg explains the Inspect and Ignore anti-pattern

Teams that know their problems but fail to do anything about them are applying the Inspect & Ignore anti-pattern and will very likely get stuck in that partner for a long time! To avoid this pattern we must invest a lot into retrospectives and learn how to effectively motivate teams to take ownership of their methods of work.
In this episode we refer to the book Agile Retrospectives by Esther Derby and Diana Larsen.

About Dominik Ehrenberg

Dominik is a Scrum Master at Infineon Technologies AG in Germany. Agile practitioner since 2008, he started in the industry as a software developer in web development and later became a Scrum Master.
You can link with Dominik Ehrenberg on LinkedIn and connect with Dominik Ehrenberg on Twitter.

Dominik Ehrenberg say: “Kanban is not a process!!!”

Sometimes we fail in very simple things like helping people understand what Agile is all about, and one instance where this happens is when teams “switch” from Scrum to Kanban. Well, the problem is that Kanban is not a process. It does not set roles are steps. In fact Kanban is about “starting where you are”, not setting a new process. In this episode we talk about how to avoid this kind of failures.

About Dominik Ehrenberg

Dominik is a Scrum Master at Infineon Technologies AG in Germany. Agile practitioner since 2008, he started in the industry as a software developer in web development and later became a Scrum Master.
You can link with Dominik Ehrenberg on LinkedIn and connect with Dominik Ehrenberg on Twitter.

Pawel Kalinowski on 2 tools that help us understand the systems we work with

In order for us as Scrum Masters to understand the systems we work within we must use concrete tools that help us understand the dynamics in play around us. Why don’t teams deliver what is expected. Can we be sure that the source of the impediments comes from inside the team? What expectations from the team regarding external help are not being met? What are the corporate policies that affect our work? Pawel shares 2 tools we can use to explore and understand the system.

About Pawel Kalinowski

Pawel Kalinowski, works with agile software development companies – currently he works with one of the largest software houses in Europe specializing in Python & JavaScript. With a background in capital markets & hedge fund industry, he knows quite a lot about risk management, which he applies in running software development projects.
You can connect with Pawel Kalinowski on twitter and link with Pawel Kalinowski on LinkedIn. You can also follow Pawel Kalinowski’s blog.

Pawel Kalinowski on the hard skills that Scrum Masters must be aware of

As Scrum Masters we developed our soft skills, our coaching skills, our conversation skills. But the teams we work with are still directly affected by the technology choices they make. As Scrum Masters we must be able to understand what teams go through to be able to help them tackle the key technical problems they must solve to be productive. That’s the topic we talk about in this episode: how to learn the hard skills.

About Pawel Kalinowski

Pawel Kalinowski, works with agile software development companies – currently he works with one of the largest software houses in Europe specializing in Python & JavaScript. With a background in capital markets & hedge fund industry, he knows quite a lot about risk management, which he applies in running software development projects.
You can connect with Pawel Kalinowski on twitter and link with Pawel Kalinowski on LinkedIn. You can also follow Pawel Kalinowski’s blog.

Pawel Kalinowski on how to organize large retrospectives

Most of the time we work with one or two teams, but sometimes we work in a larger context, where many other people are involved. How to organize a workshop for 50 people? That’s the topic we talk about in today’s episode.

About Pawel Kalinowski

Pawel Kalinowski, works with agile software development companies – currently he works with one of the largest software houses in Europe specializing in Python & JavaScript. With a background in capital markets & hedge fund industry, he knows quite a lot about risk management, which he applies in running software development projects.
You can connect with Pawel Kalinowski on twitter and link with Pawel Kalinowski on LinkedIn. You can also follow Pawel Kalinowski’s blog.

Pawel Kalinowski on the 3 types of influence we all have

When problems affect our teams, it is often very easy to focus on the problems and the reasons why it is hard or nearly impossible to change those problems. However, that is rarely the case. In most cases we have influence over the situation, even if indirectly. In fact we always have 3 types of influence over the multiple aspects of any problem: Direct influence or the things we can directly affect and/or change; indirect influence or the things we can work on with other people’s help; and finally no influence on certain things. When we act deliberately to define the aspects we can influence we are able to identify many aspects that we have impact on.

About Pawel Kalinowski

Pawel Kalinowski, works with agile software development companies – currently he works with one of the largest software houses in Europe specializing in Python & JavaScript. With a background in capital markets & hedge fund industry, he knows quite a lot about risk management, which he applies in running software development projects.
You can connect with Pawel Kalinowski on twitter and link with Pawel Kalinowski on LinkedIn. You can also follow Pawel Kalinowski’s blog.

Pawel Kalinowski on how to influence clients and help the teams succeed

There are many possible reasons for teams to fail to deliver the work stakeholders expect. However, the team – with the help of the Scrum Master – should recognize that there are impediments that can be influenced, if not solved with their own efforts. In this episode we talk about the importance of identifying what we can influence and working with the stakeholders to create involvement and therefore influence them.
In this episode we mention some important books to help us understand and achieve a good collaboration with clients. Crucial Conversations is a book about having important conversations when stakes are high and emotions cloud our judgement. How to win friends and influence people is a classic that will help Scrum Masters manage their relationships with stakeholders.

About Pawel Kalinowski

Pawel Kalinowski, works with agile software development companies – currently he works with one of the largest software houses in Europe specializing in Python & JavaScript. With a background in capital markets & hedge fund industry, he knows quite a lot about risk management, which he applies in running software development projects.
You can connect with Pawel Kalinowski on twitter and link with Pawel Kalinowski on LinkedIn. You can also follow Pawel Kalinowski’s blog.

Nikos Batsios on what makes good teams great

Coaching is one factor that affects team performance, but there are many other factors that affect teams and those other factors may be more impactful than our work as coaches. Listen to this episode to find out what factors influence team performance far beyond the work of a coach or Scrum Master.
In this episode we mention High performance team coaching and Richard Hackman’s book Leading Teams.

About Nikos Batsios

Nikos helps teams and organisations to grow strong in understanding the agile values and principles and applying various practices in their working context. Believing that great teams can achieve astonishing results. Nikos focuses on creating an environment of high quality and humane-relationships, that will further unleash the potential of individuals, enable teams to reach high performance and cooperate towards the same and shared organisation purpose.
Seeing satisfied, high performing teams that exceed their own and their organizational goals, is what motivates Nikos, and makes him want to continue serve them! He is passionate about agile coaching, motivated by learning and experiments.
Connect with Nikos Batsios on Twitter and link with Nikos Batsios on LinkedIn.