Krisztina Sajgo-Kalo and the benefits of all-in change

When a transition to Agile is ongoing there are a lot of aspects that are new to the organization. Those aspects may lead to problems later that are seen as “change resistance”. Krisztina shares with us an adoption approach that is quite different: All-in change. She describes her own journey and the benefits she observed in using that approach.

About Krisztina Sajgo-Kalo

Krisztina is a Senior IT manager with experience in several aspects of IT management on different levels as well as methodologies used. Originally from Hungary, she has worked in many countries. First as a tester, then a project manager, test manager, and many other roles.

You can link with Krisztina Sajgo-Kalo on LinkedIn.

Viyoma Sachdeva on the anti-patterns that drive fear

Are the team members afraid? Do you hear a lot of “blame” words, or “us against them” comments? This may be because some of the patterns that Viyoma describes are active in your organization. Listen to this episode to find out what those patterns are and how Viyoma tackled them in the past.

About Viyoma Sachdeva

Viyoma has over 11 years of experience in Software and Product development across different domains and phases of software development cycle. She is a certified Scrum Master and Product Owner and has worked in an Agile delivery model for the last 6 years. Her experience includes many different domains like Marketing, manufacturing, retail and Public sector and she has worked in a patent of Epidemic disease predictions.

Viyoma believes that the Agile mindset and practices are keys to solve complex problems.

You can link with Viyoma Sachdeva on LinkedIn and connect with Viyoma Sachdeva on Twitter.

Susan McIntosh describes on recurring pattern that can help you pinpoint system conditions

System conditions are patterns that happen over and over again in organizations but the teams can’t solve on their own. With Susan, we explore an approach that can help us detect those anti-patterns that can be traced back to the system, the policies, and rules set up in that organization. In this episode, we discuss a pattern of behavior in teams that can help us pinpoint the system conditions they struggle with.

About Susan McIntosh

Susan McIntosh is an agile coach and scrum master, especially interested in training and agile transformations – both fast and slow. She finds analogies to improving workplace culture in her experience in theater, teaching, cooking, and parenting. Susan is an active participant in the agile community in Denver, Colorado.

You can link with Susan McIntosh on LinkedIn and connect with Susan McIntosh on Twitter.

Sebastian Hitzler on how decision makers shape the system with lack of communication

System conditions come in many shapes and forms. In this episode, we talk about the impact of communication (or lack thereof) on the system. We discuss the case of a team that had information withheld from them, and what that led to. And Sebastian shares some great teams on how to handle the expectations of stakeholders and the teams we work with.

About Sebastian Hitzler

Sebastian works as a dedicated Scrum Master for two delivery teams at Fidor Solutions in Munich. The team members are from 10 different countries and spread into 3 different locations in Germany, Spain and Ukraine. Fidor enables clients to become digital banks based on their ecosystem. Sebastian also works with the wider organization to help them transform with lean and agile.

You can link with Sebastian Hitzler on LinkedIn and connect with Sebastian Hitzler on XING.

Barry Overeem and The 3 Pillars of Scrum

Scrum Masters are familiar with the 3 pillars of Scrum or the values that are at the core of Scrum. In this episode we discuss how focusing on those 3 pillars of scrum, the Scrum Masters can help make the system conditions visible. The system conditions are the things we must focus on uncovering and help change to enable the adoption of Agile and Scrum in the organization. After all, Scrum and Agile transformation are not easy!

About Barry Overeem

Barry, the learning facilitator as he calls his blog, considers himself a 100% Scrum Master. It’s such a comprehensive and interesting role that he gives it his full focus and keeps learning and discovering new aspects every day!

You can link with Barry Overeem on LinkedIn and connect with Barry Overeem on Twitter.

You can also check the many resources that Barry Overeem shares on his website!

Joe Anderson on how to look for cultural markers

“Culture eats process for breakfast” goes the quote. Culture is one of the big aspects of the system of work we interact with, so we need to be aware of what are the cultural trends in the organizations and teams we work with. What are those? Joe discusses with us methods and practices to identify the “cultural markers” that can help us, as Scrum Masters, understand the system we need to interact with.

About Joe Anderson

Joe is a Scrum Master at a small travel technology company with a passion for bringing out the best in people and building deep relationships. He works hard to foster an environment of safety, fun and learning with a focus on relentless improvement.

You can link with Joe Anderson on LinkedIn and connect with Joe Anderson on Twitter.

Arif Bobat 3 tools that help Scrum Masters understand the system

When joining a new team or organization we need to be aware of what is going on before we can start our efforts to help the organization. How can we do that? Arif shares with us 3 tools he uses regularly that help him understand the system and define his next actions as a Scrum Master.

About Arif Bobat

Arif is an experienced Scrum Master with a passion for enabling teams to achieve their potential, Arif loves challenging situations. In the last 5 years, he has been made redundant twice and fired twice. He is not afraid of speaking up when he sees anti-patterns and/or a lack of willingness to change behaviors.

You can link with Arif Bobat on LinkedIn and connect with Arif Bobat on Twitter.

Donald Ewart shares a simple question to detect system conditions

System conditions – which affect our teams, but are outside their control – are not always simple to tackle, but with this question, they will at least be simple to detect. In this episode, Donald shares with us a very powerful question when it comes to understanding what is affecting the teams we work with but is outside their power of influence.

We also discuss some of the anti-patterns that teams get stuck in when they don’t tackle the system conditions that affect them.

About Donald Ewart

For more than 10 years, Don has been a scrum master and coach working in different sectors in London and across the UK as an independent consultant.

With a background of 10+ years in several development roles for web and finance systems, Donald has a good technical knowledge of modern development techniques, and can quickly build rapport and respect with development teams, understanding their issues and helping them to find the right solutions.

You can link with Donald Ewart on LinkedIn and connect with Donald Ewart on Twitter. You can also find out more about Donald’s work on his website.

Venetia Foo explains the Integral Agile Model as a systems thinking tool

When looking at the team and the system conditions that affect its performance we need tools that help us understand the team beyond its physical boundaries (people, room, tools). In this episode we discuss the Integral Agile Model, introduced by Lyssa Adkins and the Agile Coaching Institute. This tool can be used as a system thinking tool to look at the team and understand that overall system that affects the teams we work with.

In this episode we refer to the book Coaching Agile Teams by Lyssa Adkins.

About Venetia Foo

Venetia has been on her agile journey since 2007 and has been a witness to the best and to the worst of it. She is passionate about learning and continuous improvement. She uses a variety of skills to empower and enable teams to perform at their best.

You can link with Venetia Foo on LinkedIn and connect with Venetia Foo on Twitter.

Balazs Tatár on how to transform the intangible systemic problems into actionable solutions

In the regular Retrospectives we find the symptoms of the systemic problems we have to face. We can use Retrospectives as the engine to find and create possible improvements to solve those systemic problems. Balazs shares his approach to Retrospectives and some examples of how he applied this approach in his work. We also discuss a critical technique to make the “intangible” problems more concrete and actionable. This technique can take your team from complaining to taking action.

About Balazs Tatár

Balazs is a technical project manager, working for the European Commission in Brussels, Belgium. Currently he plays the Scrum Master role in a support team of one of the biggest web project at the European Commission. He is a former technical lead and fan of open source technologies.

You can link with Balazs Tátár on LinkedIn and connect with Balazs Tátár on Twitter.