Developing Teams the Scrum (and Lean) way! by Lean.Org’s The Lean Post

I’ve been working on a collection of great blog posts about the Scrum Master role. If you have a favorite article on the Scrum Master role, or it’s goals and responsibilities, let me know by submitting it here: https://bit.ly/TheBestScrumMasterBlogPosts2020

Scrum Masters are key participants in the teams, and key contributors to the improvement of productivity in the organizations they work in. Even if the Scrum approach and Agile, in general, are very new (from late1990’s, early 2000s), there are other approaches that have been with us for nearly more than a century now.

One such approach is “Taylorism”. In that approach, the main premise is that “some people” know “what needs to be done and how” (the planner/thinker), and other people “do it” (the doers).

“Take it to the team”: a Scrum Master Mantra

Unfortunately, that Tayloristic approach has become prevalent thanks to the work of some early consultancies.

In Scrum, one of the most important changes to the world of work is that the “doers” are also the “thinkers”. This is one of the reasons why here on the Scrum Master Toolbox Podcast, we often say: “take it to the team”. In other words, anyone can raise an idea of improvement, but only the team knows what can/should be done to achieve the goal. Sometimes that team is the development team, sometimes it is the development team + stakeholders, but it’s “the team” that owns and develops the process of work.

This perspective is revolutionary for many, including many consultancies that still push “process improvement” à lá Taylor (you know which ones).

What’s better than Taylorism for developing our teams and organizations? 

That’s why I want to highlight this post in Lean.Org’s Lean Post blog: “Develop Your People Patiently Rather Than Rely on Super Taylorism”

As the article puts it: while the “west” was focused on separating the thinking from the doing, and using “Super Taylorism”,  “in Japan, Toyota was developing a different approach to strategy, one based on technical learning on the gemba through trial and error–a process that aimed to serve all customers with a broad product line of high quality and at the right price.”

Does that sound familiar? Scrum is exactly that kind of approach: “based on technical learning on the Gemba through trial and error”

Check out the post, and learn about the roots of Scrum and Agile. Don’t get stuck in a Tayloristic approach that leads to frustration, dis-enfranchising the team, and long term problems.

Help us grow as a Scrum Master community, share your best 2020 articles below.

Maximilian Fritzsche on the rule-driven culture and its impact on Scrum adoption

How would Scrum apply to a culture where the rule is to set more rules. To cover all angles, and to be prepared even for very unlikely scenarios?

In this episode we discuss how Scrum can survive in a culture like the German culture, where people want to have rules for many reasons, and want to prevent all possible mistakes with those rules.

We discuss what might be the impact, and how to adapt, and learn from that cultural perspective.

Rules are good, but how much should we focus on rule-setting vs adapting to the unknown?

About Maximilian Fritzsche

Maximilian worked as a Scrum Master for several years and believes that the way to look at the role is to always have in mind the following quote: “Keep moving forward” – his favorite quote, and what he tries to do every day. “One step at a time!”

You can link with Maximilian Fritzsche on LinkedIn.

Abbas Ghahremani on the value of respect and the goals for hierarchy in Scrum teams and Agile organizations

From respect (a Scrum value) to hierarchy there’s often a very short route. But what is the role of hierarchy in our organizations? Why is it there, what is the benefit we get from it, what is the goal it tries to achieve?

Abbas invites us to think about the role of hierarchy in our organizations, and in our culture. From a multi-cultural background, Abbas explores what hierarchy and respect mean for him, and how it affects the teams and organizations we work with.

In this episode we refer to TEAL organizations, a term that is based on the book: Re-inventing organizations by Frederic Laloux.

About Abbas Ghahremani

Abbas is a Scrum Master who enjoys coaching individuals and teams who are on a journey of developing an agile mindset, focusing on values and principles which will make them work lean, collaborate and generally enjoy work more!

He calls himself an agile and product person focusing on delivering value early and often to customers.

You can link with Abbas Ghahremani on LinkedIn or follow Abbas Ghahremanni on Instagram.

Andrew Hudson how organizations help or hinder collaboration at the team level

Collaboration is an often used work to explain how teams can reach their goals. So much so, that we, as Scrum Masters, very often work on improving collaboration. However, collaboration is really a series or trade-offs. In this episode we explore the organizational forces that help or hinder collaboration in our teams.

About Andrew Hudson

Andy is a Scrum Master within the Media industry. He’s passionate about making work a motivating, enjoyable and empowering place to be. He wants to help teams and individuals reach their full potential and believes developing the right vision and mindset is more valuable to effective teams than any process or framework.

You can link with Andrew Hudson on LinkedIn and connect with Andrew Hudson on Twitter.

Gilberto Urueta on how to deal with the pressures the system puts on Scrum Masters

Scrum Masters are roles in an organization, and as such, it is affected by the same pressures that every person in the organization suffers from. In this episode we talk about the CTO that wanted the Scrum Master to “push change” into the organization and what that means for the role.

In this episode we refer to the interview with Karin Tenelius, where she details how we can bring difficult topics into the conversation in a constructive manner.

About Gilberto Urueta

Gilberto is a Berlin-based Scrum Master. He is passionate about Agile, Lean, Scrum and most of all complexity. He is currently working at Takeaway, a leading online food delivery marketplace in Continental Europe.

You can link with Gilberto Urueta on LinkedIn and connect with Gilberto Urueta on Twitter.

Zeshan Ilyas on how department silos destroy a Scrum team’s productivity

Scrum teams can be very productive. Some teams can deliver working software to customers or production several times per day. However, some Scrum teams are stuck, unable to deliver and reach high levels of productivity.

Silo departments, functionally aligned, but separating end-to-end activities can destroy a Scrum team’s ability to reach their potential. In this episode we discuss some of the reasons why that is, and what we, Scrum Masters, can do about it.

About Zeshan Ilyas

With a firm focus on Agile and Scrum methodologies, Zeshan has worked within high profile organisations, including the HSBC, Capgemini Financial Services, Talk, Talk, and many more.

Having worked with Agile companies for many years, Zeshan identified a need for a community of Agilists in Pakistan, which would bring together professionals adopting an Agile or Scrum approach, help increase awareness of Agile.

You can link with Zeshan Ilyas on LinkedIn and connect with Zeshan Ilyas on Twitter.