From Mechanics to Human Factors—How Scrum Masters Grow | Pascal Papathemelis

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches Episode: From Mechanics to Human Factors—How Scrum Masters Grow | Pascal Papathemelis
Host: Vasco Duarte
Release Date: July 7, 2025

---

Introduction

In this episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Pascal Papathemelis, an experienced Agile Coach from Finland. The conversation delves into Pascal's journey from a project manager to a Scrum Master, highlighting his insights on the evolution from focusing on Scrum mechanics to prioritizing human factors within Agile teams.

---

Guest Introduction: Pascal Papathemelis

Vasco Duarte (01:11):
"He’s an agile and professional coach that wants to make a positive impact to the people working with him. He's coaching in Finnish, German, and English, focusing on human factors, outcomes, effectiveness, flow, decision making, clarity, and constant improvement."

Pascal Papathemelis (02:01):
"I ended up being a project manager and then transitioned to an Agile coach, helping others with my experience. I’m certified by the International Coaching Federation and focus on both agile coaching and professional coaching."

---

Pascal's Journey to Becoming a Scrum Master

Pascal shares his transition from a computer science graduate working at Nokia to becoming a Scrum Master. Initially involved in IT programming, he discovered a knack for project management and soon sought ways to enhance his management skills. His introduction to Scrum in 2005 resonated with his empirical experiences, leading him to embrace Agile methodologies fully.

Pascal Papathemelis (02:01):
"When I got introduced to Scrum in 2005, I realized many of the things I had discovered empirically aligned perfectly with Scrum’s principles. This sparked my deep interest in Agile, eventually leading me to become an active member of the Agile Finland association and later an Agile coach."

---

Challenges and Early Failures in Agile Implementation

Pascal reflects on his initial attempts to implement Scrum, focusing primarily on its mechanics. Early teams struggled to achieve sprint goals, with stories spilling over from one sprint to another and urgent tasks disrupting planned work.

Pascal Papathemelis (05:18):
"The first teams I worked with in Scrum were not very good at achieving the sprint goal. Stories were floating from one sprint to the next, and we were taking in urgent things that disrupted our workflow."

Through retrospectives and incremental improvements, Pascal and his teams began to align better with sprint objectives by refining backlog management and breaking down tasks more effectively.

---

Shift from Scrum Mechanics to Human Factors

Over time, Pascal recognized that the success of Agile teams hinges more on human dynamics than on strict adherence to Scrum mechanics. He emphasizes the importance of understanding team members as individuals with unique needs, behaviors, and interpersonal dynamics.

Pascal Papathemelis (07:03):
"Involving everyone in the Scrum team, listening to each other, collaborating well, developing people’s skills and attitudes, and checking the team chemistry are now more important than the detailed mechanics of Scrum for me."

---

The Importance of Human Factors in Agile Teams

Pascal elaborates on why human factors have taken precedence in his coaching approach. Recognizing that each team member has good intentions but may face conflicts or personal challenges, a Scrum Master must foster strong interpersonal relationships and create a supportive environment.

Pascal Papathemelis (07:51):
"Every person in the team is an individual with good intentions, but there are often conflicts and clashes. A good Scrum Master should be capable of sensing when something is wrong with a person and find a suitable moment to address it."

He shares an anecdote about having informal conversations during coffee breaks to build rapport and understand team members' states, which in turn helps him better facilitate meetings and accommodate individual needs.

Pascal Papathemelis (09:00):
"Before COVID, I found that the biggest breakthroughs happened in the corridor or at the coffee machine. These informal discussions allowed me to understand what was affecting a person and adjust my facilitation accordingly."

---

Strategies for Team Formation and the Startup Phase

Pascal places significant emphasis on the initial formation of Agile teams. He advocates for a strong startup phase to establish trust and set clear goals, which can prevent prolonged periods of conflict (storming phase) and accelerate team cohesion.

Pascal Papathemelis (10:51):
"Without a good start, you might jeopardize the forming stage and prolong the storming phase. A good startup ensures that the team builds trust early on, making the transition to performing much smoother."

He draws inspiration from Diana Larsen, highlighting the importance of visualizing team information and clarifying goals during the kickoff phase.

Pascal Papathemelis (11:10):
"Visualizing information is like a picture is worth more than a thousand words. Clarifying the common goal ensures that everyone is targeting the same direction and committed to achieving it."

Pascal also emphasizes the role of retrospectives in refining team agreements and continuously improving workflows, acknowledging that initial setups don't need to be perfect.

Pascal Papathemelis (12:00):
"Working agreements don’t need to be perfect from the start. What’s important is to show that everyone is human, allowing team members to check in and express their weaknesses, fostering a sense of mutual support."

---

Conclusion

The episode wraps up with Pascal expressing gratitude for the opportunity to share his experiences and insights. Vasco Duarte encourages listeners to explore further discussions on the importance of the startup phase by referencing an episode with Arne Rock.

Vasco Duarte (13:15):
"Thank you for sharing all of those stories with us, Pascal."

Pascal Papathemelis (13:19):
"Yeah, thank you."

---

Key Takeaways

1. Transition from Mechanics to People: Effective Scrum Masters recognize that human dynamics are crucial for team success, often more so than rigid adherence to Scrum processes.

2. Importance of the Startup Phase: Establishing trust and clear goals from the outset can significantly reduce conflicts and enhance team performance.

3. Continuous Improvement Through Retrospectives: Regular reflection helps teams refine their processes and work agreements, fostering a culture of continuous improvement.

4. Building Rapport: Informal interactions, such as coffee breaks, can provide valuable insights into team members' well-being and enhance team cohesion.

5. Adaptability and Empathy: Scrum Masters must be adaptable and empathetic, addressing individual team members' needs to maintain a productive and harmonious work environment.

---

Quotes with Timestamps

• Pascal on Transitioning to Agile Coaching (02:01):
  "When I got introduced to Scrum in 2005, I realized many of the things I had discovered empirically aligned perfectly with Scrum’s principles."

• Pascal on Early Challenges (05:18):
  "The first teams I worked with in Scrum were not very good at achieving the sprint goal."

• Pascal on Human Factors (07:03):
  "Involving everyone in the Scrum team, listening to each other, collaborating well, developing people’s skills and attitudes, and checking the team chemistry are now more important than the detailed mechanics of Scrum for me."

• Pascal on Sensing Team Dynamics (07:51):
  "A good Scrum Master should be capable of sensing when something is wrong with a person and find a suitable moment to address it."

• Pascal on Team Formation (10:51):
  "Without a good start, you might jeopardize the forming stage and prolong the storming phase."

• Pascal on Visualizing Information (11:10):
  "Visualizing information is like a picture is worth more than a thousand words."

---

This episode provides valuable insights for Scrum Masters and Agile Coaches, emphasizing the pivotal role of human interactions and team dynamics in achieving Agile success. Pascal Papathemelis's experiences underscore the importance of empathy, continuous improvement, and strategic team formation in fostering high-performing Agile teams.

Transcript

[Vasko]

Hey there, agile adventurer, just a quick question. What if for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership and it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership, that's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[Podcast Host]

Hello everybody. Welcome to one more week of the Scrum Master Toolbox Podcast. And this week joining us from Finland is Pascal Pavatemylis. Hey Pascal, welcome to the show.

[Pascal Pavatemylis]

Nice that you have me with you.

[Podcast Host]

So I've known Pascal for a long time. It's incredible that he's joining us on the podcast only now. He's an agile and professional coach that wants to make a positive impact to the people working with him. He's coaching in Finnish, German and English and his focus areas are human factors, outcomes, effectiveness, flow, decision making, clarity and constant improvement. So Pascal, that was a short intro. Tell us a little bit more about yourself and how did you end up becoming a Scrum Master?

[Pascal Pavatemylis]

Yeah, well, I'm. I moved to Finland after graduating university for private reasons and worked at Nokia. I graduated from, from computer science and so I worked in IT programming. But quite soon I realized I was good in talking and dealing with people. So I ended up pretty fast being a project manager. And then I've been always looking like different ways of how to improve project management and be better in my work. And then when I got introduced 2005, I think it was Scrum, I realized that, hey, many of those things I've been found out empirically myself, but it's not worth planning too far ahead. And the focus was like the last week in the learnings of that and focusing on the next week and get the team that I was working with in a good state of flow. So I pretty much got hooked immediately because that was like the first time I saw that there was a great association with what I was already doing and it resonated with me and my way of thinking ever since I became more and more interested into agile and so I ended up being active member in the Agile Finland association. And then at some point I totally switched from being a project manager working in an agile way to being an agile coach and helping others with my experience. So here I am working as an Agile coach and I've done in the meantime also professional coaching education and I'm a member of the ICF Finland chapter certified by icf. And I also do like coaching without an agenda where an agile coach has an agenda to a certain objective and help and teach others and make them better in the way they work. When I'm a professional coach, I try to be more neutral and the coachee brings the goals what they are.

[Podcast Host]

And ICF stands for International Coaching Federation.

[Pascal Pavatemylis]

Federation. Yes. Yeah, very good.

[Podcast Host]

So of course that's a storyline that is familiar to many of our listeners, I'm sure starting from a computer science background, discovering project management, eventually figuring out that hey, this SCRUM thing, it might actually work. That's something that I have also gone through myself. So when we go through that journey though it's not always simple or easy to progress in that journey. Right. And sometimes we do face failure and today's failed Monday here on the podcast. So we want to explore one of those stories, Pascal. A story of a moment that was particularly hard, difficult, a story of failure of course, because we can learn from that and hopefully avoid those mistakes ourselves in the future. So tell us that story, Pascal.

[Pascal Pavatemylis]

Probably I have many stories what what I've been thinking like over time in the beginning I was focusing more on the mechanics of Scrum and we the the first teams I had in work I've been working with in Scrum, they have been not very good in achieving the sprint goal. Stories were floating from one sprint to the other. We had have been taking in urgent things in the sprint, so that did not work very well. Then over time we've been a bit better in improving through the retrospectives and identifying and doing small improvements in, in achieving the, the sprint goals and, and not having so much discrepancy from what we wanted to do from what we were doing. So that was kind of the first learning, not taking too much into the sprint and, and being more thorough in, in breaking down the product and the backlog into small stories that everybody in the team is confident that it can be achieved within one sprint later on. I've experienced also challenges even though that was there, but then I Think my focus recently has more changed to be on the human factors.

[Podcast Host]

What do you mean by human factors, Pascal?

[Pascal Pavatemylis]

Yeah, I mean like involving everybody into the SCRUM team, into the refinement, listening to everybody, having people collaborating well, developing the skills of the people, their attitudes, checking the chemistry and so nowadays I think those are more important than all the mechanics of Scrum.

[Podcast Host]

Why did you come to that conclusion that those human factors, as you describe them, are actually more important than the detailed mechanics of what Scrum is?

[Pascal Pavatemylis]

Because you have. Every person in the team is an individual and from the, to start with, I have the. I assume that every individual has a good intention to, to do work well and be a master in what he's doing. But there are often conflicts and clashes. People might not be aware of something. So thinking like people might have certain needs and might behave they, they might have good days and bad days. So SCRUM Master must be in a good contact and know the team members so that he can take into account those different. Good SCRUM Master should be capable to sense when a person, something is wrong with the person and then perhaps find a good suitable place or moment to, you know, confront the person and find out what's going on. Before COVID I was, when I was working with teams, I said that the biggest breakthroughs took place in the corridor at the coffee machine because then when I could see, sometimes he behaves now strange. Then when I saw that he's going for a coffee, I went also for a coffee. Not because I wanted a coffee, but because I wanted to have a discussion in a safe environment with the person and ask, okay, what's going on with you? And then I get the little tiny bit of information that might be affecting that person. Then I can better take that into account when I facilitate the meeting on the rest of the day and better include that person or take the needs that he has during that day and accommodate better for those. I mean, we all are humans and might have outside work related things that affect us. Yeah. So and then I've been putting more effort in how to start a team in the beginning. So without having a good start, you might jeopardize kind of the. It might take more effort on getting the team into a good forming stage. Of course we have forming, norming, performing all those different phases the team goes through, but without a good start where we get to create the trust, then I could see that the storming phase might take longer time and we want to have the storming phase not take that long time.

[Podcast Host]

When you think about that beginning or the startup phase for a team? What are the models that you look to these days to inspire you in how to focus on that aspect that beginning the setting up of the team.

[Pascal Pavatemylis]

I've enjoyed the things that Diana Larsen brought up. Diana Larson is mostly known for the retrospective book, but she is also known for the startup how to start up Teams in the beginning so not afterwards reflecting but beforehand trying to make a good a good start and ensure that things go well. So it's good to understand like who who is part of the team. Clarify that perhaps in the kickoff not everybody's present or there might be some people who might not have they might be in the gray zone. So it's good to visualize that. I like visualizing the information. So it's a picture test more than a thousand words and then clarify what is the goal. So without a common goal you might not target the same direction and get a commitment to that goal. And then working on how the team would like to work. Of course in the beginning, without having experience together, this might not be the team might not know upfront of how things will go and what would work best for them. But that's why we have the retrospective to then refine those working agreements and improve over time. So this doesn't need to be perfect. But it's good to show that everybody's human. The check in to show also weaknesses and give like a sense that nobody, no team member is perfect.

[Podcast Host]

Yeah, absolutely. It's a great point to make. I'll put the link in the show. Notes to also an episode we had with Arne Rock who describes the importance of putting the emphasis on the startup phase of a team. Thank you for sharing all of those stories with us. Pascal.

[Pascal Pavatemylis]

Yeah, thank you.

[Vasko]

Alright, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you, the members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile every day. We're talking access to over 700 hours of agile Gold, CTO level strategy talks, Summit keynotes, live workshops, E courses, Deep dive interviews, books. And if you're into no estimates, we got the pioneers of no estimates in those Deep Dive interviews as well. Agile business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the [e-mail] membership because listening is great, it's important. But doing it together, that's next level. I'll see you in the community.

[Podcast Host]

Slack we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is key.

[Vasko]

Carry.