People, Trust, and Humor: Insights from “Kostiantyn Sobakar, Scrum Master bei Elektrobit”

A talk that brings the human core of the Scrum Master role into focus

In the session “Kostiantyn Sobakar, Scrum Master bei Elektrobit,” the person behind the role steps into the spotlight. Kostiantyn Sobakar doesn’t talk about framework diagrams or agile dogma; he talks about people. About differences, about the slow work of building trust, about staying committed to learning, and about using humor as a bridge when things get tense. From our DevJobs.at editorial vantage point, that human-centered emphasis defined the tone of the conversation.

What struck us immediately was how naturally Sobakar grounds the reality of Scrum Master work. He names challenges without drama, identifies essential skills without buzzwords, and connects practical advice to a clear stance: openness, empathy, continuous learning, and a willingness to live with the role’s duality—the talk-heavy side and the system-shaping side.

The essence: the role is deeply human—and precisely for that reason, demanding.

The human at the center: working with personalities

Sobakar paints a picture of teams as living systems, where distinct personalities collide and grow together. That starting point isn’t a hurdle—it’s the actual stage for Scrum Master work. He notes how differently people respond to “the same words” or “the same situations,” a reminder that context and timing matter and situational judgment is key.

Practically, we see three immediate implications:

• Language is contextual. The same sentence can inspire or trigger resistance, depending on person, timing, and relationship.
• Relationships aren’t produced by rituals but by attention and resonance. Those who listen build bridges.
• Progress is often quiet. It’s not the “perfect” retrospective that resolves tension but the persistence to attune to one another in the everyday.

Sobakar also points out how relationships mature over time. What starts out difficult can turn into closeness through steady collaboration and mutual observation.

Embedded in that is a reminder to be patient. Collaboration is a process. Teams aren’t machines you calibrate once. They are social systems—responsive to signals and sustained by time.

Trust as a two-way commitment

Trust repeatedly anchors Sobakar’s statements—not as a buzzword, but as a working condition without which openness and ownership won’t take root.

Mutual is the key word. Trust isn’t something a Scrum Master merely demands of a team; it’s also a self-commitment. In practice, that looks like this from our vantage point:

• Tame the urge to control: don’t require constant proof; create real autonomy.
• Respect decisions made close to the work—even if your personal solution would have been different.
• Be transparent about assumptions and limits: stating what you trust enables reciprocity.

Trust is visible not in dashboards but in behaviors: Is ownership genuinely practiced? Are mistakes recognized as learning moments? Here, Sobakar’s emphasis on empathy becomes decisive.

Communication and empathy: the non-negotiables

Sobakar is explicit:

Being communicative here doesn’t mean talking more; it means bridging deliberately by listening, asking, and enabling shared understanding. Open ears and empathy translate into practices any team can feel immediately:

• Ask before judging.
• Treat conflict as information, not as a disturbance.
• Respect differences in pace and style—and turn them into assets.

Empathy isn’t a nice-to-have; it’s the operating system of the role. It helps separate intent from impact and turns basic moderation into real facilitation: spaces where others can think, speak, and decide clearly.

Lifelong learning: keeping momentum—and the conditions that make it possible

A second leitmotif for Sobakar is ongoing development:

He ties that directly to the conditions available at Elektrobit:

This is a double message: learning is first a personal stance—stay curious, try new things, update your mental models. And learning is also a cultural and structural issue—time and opportunities must concretely exist. Sobakar names both. That balance is valuable because it distributes responsibility fairly: individuals bring the will; organizations provide the frame.

For a Scrum Master’s day-to-day, several lines follow:

• Prefer regular small learning pulses over rare, oversized “training blocks.”
• Treat knowledge sharing as a language-building exercise: it aligns terms and reference points.
• Plan learning like work: if it’s not scheduled, it’s left to chance.

Two faces of the job: conversation spaces and ticket tools

The role becomes especially concrete when Sobakar describes the dual nature of the Scrum Master’s days:

That’s not a contradiction—it’s the rhythm of the job: people work and system work. Conversations where understanding and decisions emerge. And tool work where flow, structure, and transparency are maintained. Live only in meetings and you lose structure; live only in the tool and you lose the people. The value sits in the alternation.

We see a few useful principles here:

• Calibrate your week: plan blocks for system focus (backlogs, boards, metrics) and for people focus (1:1s, team formats, ad-hoc conversations).
• Use tools as mirrors, not cages: boards reflect how the team works—don’t let them dictate it.
• Choose deliberately what’s synchronous and what’s asynchronous: not every topic needs a meeting; not every misunderstanding can be solved in comments.

Sobakar normalizes a reality many recognize—and that’s liberating. The job isn’t romantic; it alternates between loud and quiet, social and analytical, facilitation and structure.

Openness and experimentation: advice for aspiring Scrum Masters

When Sobakar offers advice, it’s simple and direct:

Being open means not starting with the answers. Being communicative means constructing the bridges intentionally. Trying new things means testing hypotheses—in retrospectives, planning formats, and stakeholder conversations. The message is pragmatic: progress comes from small experiments and shared learning, not from the perfect deck.

This stance helps especially in contexts where teams bring varying levels of maturity and expectations. Stay open and you’ll discover patterns rather than impose them. Experiment and you’ll find what serves the context. Communicate and you’ll generate trust in the process.

Humor as a problem-solving force

One of the most memorable lines in the session is about humor:

Humor here isn’t about cracking jokes—it’s a stance that creates distance, lightness, and connection, particularly when tension is high. In meetings where pressure builds, humor can make the room human again. In conflicts that start to calcify, humor can remind people of what they share. The rule of thumb: never at someone’s expense, always in service of the space.

Practically:

• Spot the right moment: humor is a release valve, not a distraction.
• Be kind, never cynical: cynicism destroys psychological safety.
• Take the work seriously, not yourself: self-deprecation de-escalates without trivializing the issue.

Takeaways for developers, Scrum Masters, and teams

From “Kostiantyn Sobakar, Scrum Master bei Elektrobit,” several actionable signals emerge—without magic formulas, but with real leverage.

For aspiring and practicing Scrum Masters

• Listen twice: to content and to relationships. What’s said and how it lands are two different data streams.
• Trust first, verify later. Proof follows action, not the other way around.
• Schedule learning like delivery. Workshops, trainings, knowledge sharing aren’t side quests.
• Balance meetings and tool work. Both are system-shaping work.
• Cultivate humor as a team skill. It lightens the heavy without making it small.

For developers and product people

• Surface differences early—speed, understanding, expectations. That prevents rework.
• Use the board as a conversation starter: contradictions between plan and reality belong in the open.
• Give and ask for trust. Make it mutual.
• Make space for learning. Share what you learn; ask what others are learning.

For organizations

• Provide time and opportunities for learning—concretely enough that teams can plan around it.
• Read trust in behaviors, not metrics.
• Recognize the dual nature of the Scrum Master role: relationship work and system work are equally valuable.

What this teaches us about team dynamics

Sobakar points to a view of teamwork that lives beyond method checklists. People work differently. Relationships take time. Trust is a practice. Communication often means listening more than talking. Learning is ongoing. Humor is a catalyst.

These elements reinforce each other. A team that practices trust can speak about problems earlier. Open communication accelerates learning. What’s learned shows up in smoother workflows—and in tools that reflect reality more clearly. Humor helps carry the inevitable friction. The outcome isn’t perfection but resilience: the ability to stay effective amid uncertainty.

The day-to-day: decisions, improvements, planning

Sobakar talks about days filled with meetings and decisions, and about days spent adapting and improving tools like Jira. That’s the bread-and-butter of the role:

• Support decisions: create clarity, sort options, bring the right people together.
• Improve workflows: sharpen ticket slices, make WIP visible, structure priorities.
• Enable planning: assess capacity, surface risks, make trade-offs explicit.

It may sound unspectacular—and that’s exactly the point. Effectiveness shows up in everyday moves, not grand gestures. And it shows over time, just as in Sobakar’s example where initial friction matures into trust and closeness.

Continuity over hype: why this stance endures

The session’s lasting value is its immunity to hype. No new framework, no fancy jargon, no cure-all. Instead, principles that hold in any context:

• Take people seriously.
• Practice trust.
• Make communication and empathy non-negotiable.
• Institutionalize learning.
• Cultivate humor.

These aren’t glamorous, but they’re durable. Leaning on them helps resist the temptation to fight complexity with more complexity. Instead, you build a culture that stays effective in uncertainty.

Quotes that stick

Several of Kostiantyn Sobakar’s lines linger as anchors for practice:

Together they draw a portrait of a role that is both grounded and human—and powerful precisely because of that.

Conclusion: A clear compass for Scrum Mastery

“Kostiantyn Sobakar, Scrum Master bei Elektrobit” reminds us that the essentials are simple—and demanding in execution. Work with people requires patience and presence. Trust requires courage and consistency. Learning requires time and structure. The job alternates between conversation spaces and structured tools. And humor makes the heavy a little lighter.

From an editorial standpoint, our takeaway is clear: if you want to be effective in this role, build relationships, hold the frame, keep learning—and keep a smile handy when things get tricky. That’s the maturity of a Scrum Master: the ability to hold both sides of the work together and strengthen the people within it.

• 

  

  Introduction and Trends in Automotive Software

  Dr. Georg Gaderer von Elektrobit gibt in seinem devjobs.at TechTalk einen Überblick zum Thema Automotive Software und spricht über zukünftige Trends in diesem Gebiet.

  Watch now

• 

  

  Dr. Michael Ziehensack, Vice President Automotive Networks bei Elektrobit

  Vice President Automotive Networks bei Elektrobit Dr. Michael Ziehensack erzählt im Interview darüber, wie die Devteams im weltweiten Unternehmen die Software entwickeln, was dort Herausforderungen sind und auf was der Fokus beim Recruiting liegt.

  Watch now
• 

  

  Nikolaus Donath, Technology Team Manager bei Elektrobit

  Nikolaus Donath von Elektrobit gibt im Interview Einblicke in die Rolle als Technology Team Manager und spricht über den Aufbau des Teams.

  Watch now

• 

  

  Aleksandra Konopacka, Software Engineer bei Elektrobit

  Aleksandra Konopacka von Elektrobit spricht im Interview über ihren ursprünglichen Zugang zum Programmieren, was ihre aktuelle Arbeit beinhaltet und gibt Hinweise für Anfänger.

  Watch now
• 

  

  Johannes Balog, Embedded Software Engineer bei Elektrobit

  Johannes Balog von Elektrobit erzählt im Interview über seine Laufbahn – von den holprigen Anfängen in der HTL bis hin zu seiner aktuellen Arbeit als Embedded Software Engineer – und gibt Ratschläge für Beginner.

  Watch now
• 

  

  Michael Wegner, Senior Software Developer bei Elektrobit

  Michael Wegner von Elektrobit erzählt im Interview über seine Tätigkeit als Developer für Automotive Software, welche Challenges es hier gibt und gibt Tipps für Neueinsteiger.

  Watch now
• 

  

  Miriam Leopoldseder, Software Engineer bei Elektrobit

  Miriam Leopoldseder von Elektrobit erzählt im Interview über ihren Background im Programmieren, gibt Einblicke in das Embedded Hardware Development Team, in dem sie aktuell arbeitet und gibt Tipps für Neueinsteiger.

  Watch now