Get your EARLY BIRD ticket to the Global Agile Summit Now!

Register now!

Viktor Glinka: From Component Teams to Cross-Functional Teams — How to Navigate the Hardest Agile Transformation

“Our customers do not buy our components. They use the product as a whole. And when it comes to integration, the real problem pops up.” – Viktor Glinka

Viktor brings a challenge many Scrum Masters face: transitioning from component teams to cross-component, cross-functional teams in a large-scale Scrum setup.

Picture 8 to 10 teams, each owning their own part of the system, never touching anything else — and the company stuck in delivery for months. The premise behind component teams sounds logical: specialization leads to speed. But as Viktor explains, that speed is local — optimized for the component, not the product. When integration time arrives, responsibility gaps appear, rework multiplies, and teams start identifying with their components rather than the product. “We’re the billing team — we don’t deal with anything else.”

When they reorganized into cross-functional teams, the complaints were immediate: “I was really productive before, and now I can’t finish anything.” Viktor and his fellow Scrum Masters took a two-pronged approach. First, they secured time credit from leadership — a couple of months where learning was prioritized over deadlines.

They ran mob programming sessions, coached teams, and removed impediments. Second, they shifted focus from outputs to outcomes, organizing customer interviews that helped developers understand what users actually needed.

The development director reinforced this by joining refinement sessions, telling teams: “You might not need to develop anything if it still satisfies the customer need.” The result was a shift from transactional stakeholder relationships to genuine cooperation, and teams that began to see beyond their component boundaries.

Self-reflection Question: If your teams are organized around components, what would it take to run one experiment — just one sprint — where a team picks up work outside their usual component? What would you need to make that safe?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Viktor Glinka

Viktor GlinkaViktor is an organisational consultant and Professional Scrum Master who helps teams and leaders find simpler ways to deliver value while keeping the human side of work at the center. He’s practical, curious, and focused on real outcomes rather than buzzwords. His true passion is adaptability – both in business and in personal life.

You can link with Viktor Glinka on LinkedIn.

Viktor Glinka: When Internal and External Team Members Have Divergent Goals — The Silent Killer of Agile Teams

“The root causes for destructive team patterns often lie outside the team itself.” – Viktor Glinka

Viktor shares a story from a manufacturing organization where one team stood out — and not in a good way. The team was composed of both internal and external members, and what no one saw coming was that their implicit goals were fundamentally divergent: the external members were focused on maximizing revenue for their own company, while the internal members cared deeply about product quality.

The signs were visible to anyone who approached them — they barely talked to each other and preferred to work individually. When Viktor tried to raise the topic of cooperation and trust, he was met with awkward silence. One team member finally told him: “I don’t want the team to blow up. In my previous experience, I raised this topic and that was the end of the team.” Fear kept the truth underground.

Viktor brought his observations to the manager, who acknowledged the lack of a shared goal as the root cause — but couldn’t fix it because he wasn’t authorized to manage the external people.

The takeaway was clear: three key success factors for any team are the right team composition with people who want to work together, a shared goal that unites diverse perspectives, and clear expectations set by their manager.

In this segment, we talk about LeSS self-designing team workshops and the importance of team composition in scaled setups.

Self-reflection Question: Does your team have a shared goal that everyone — including external members and contractors — genuinely understands and cares about? When was the last time you checked?

Featured Book of the Week: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland

Viktor recommends The Art of Doing Twice the Work in Half the Time by Jeff Sutherland as the book that sparked his passion for Scrum. As he puts it: “I know the title is very controversial and often criticized, but I could deeply relate to the stories inside the book. They sparked a passion that is still with me.”

Viktor also recommends a bonus book: Reinventing Organizations by Frederic Laloux, which showed him the real power of self-organization and validated what he had already started experimenting with in his project management career. It pushed him to explore holacracy, sociocracy, intent-based leadership, and coaching.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Viktor Glinka

Viktor GlinkaViktor is an organisational consultant and Professional Scrum Master who helps teams and leaders find simpler ways to deliver value while keeping the human side of work at the center. He’s practical, curious, and focused on real outcomes rather than buzzwords. His true passion is adaptability – both in business and in personal life.

You can link with Viktor Glinka on LinkedIn.

Viktor Glinka: When Passion Becomes the Problem — How Pushing for Agile Change Too Fast Creates Resistance

“I wanted to change the organization overnight with my eagerness and passion. Instead of helping the system to evolve, I created resistance. I became the problem myself.” – Viktor Glinka

Viktor shares one of the most honest failure stories we’ve heard on the show. Early in his Scrum Master career, he joined a finance organization as a Scrum Master for a newly created department — his first experience in a scaled setup. Each team owned a particular part of the user journey, organized around components.

After getting exposed to Large-Scale Scrum (LeSS) through a colleague, Viktor became overexcited. He started pushing for structural changes daily, telling the head of department that the current team composition was wrong and they needed cross-functional feature teams. But he was disconnected from reality.

For this particular organization, even having partially cross-functional teams was already a big stretch. Worse, the head of department wasn’t even authorized to make the changes Viktor was pushing for. Instead of helping the system evolve, he created resistance.

What proved his approach wrong? That same department later received a European Award for being the best mortgage department. It took Viktor a few more years and similar cases to fully absorb the lesson: read the room, develop sensitivity to the system’s pace, and stimulate reflection in decision makers rather than pushing your own agenda.

In this episode, we refer to organizational development, LeSS (Large-Scale Scrum), and systems analysis. Viktor also mentions the interview with Bas Vodde on the Scrum Master Toolbox Podcast.

Self-reflection Question: When was the last time you pushed for a change because you believed it was right, without checking whether the system was ready for it? What would happen if you started by asking decision makers what they think would be a good next step?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Viktor Glinka

Viktor GlinkaViktor is an organisational consultant and Professional Scrum Master who helps teams and leaders find simpler ways to deliver value while keeping the human side of work at the center. He’s practical, curious, and focused on real outcomes rather than buzzwords. His true passion is adaptability – both in business and in personal life.

You can link with Viktor Glinka on LinkedIn.

BONUS: From 3,000 Scripts to 3 Tools – Building AI-Last Software With Conversational AI Pioneer Peter Swimm

 

In this special BONUS episode, Peter Swimm—conversational AI veteran, creator of BotKit (the open-source chatbot framework that powered Slack and Teams bots), and former Principal Product Manager at Microsoft Copilot Studio—shares what 25+ years in tech taught him about working with AI. From his brutal experiment of running an entire business on voice-based AI for a week, to why he treats AI more like R2-D2 than C-3PO, Peter offers a grounded, practical perspective on where AI fits in software development teams.

From BotKit to Copilot Studio: A Front-Row Seat to the AI Evolution

“We had the number one bot in the Slack app store, because there were only 8 bots, and ours used regex. To show you how far we’ve come.”

Peter’s journey into conversational AI started with a newspaper ad and a creative writing background. When Slack launched its API, Peter and BotKit co-creator Ben Brown immediately saw that building bots wasn’t just a technical challenge—it was a social and creative one, like writing scripts for plays that interface with people in their daily lives. That insight powered BotKit into becoming the backbone of Slack and Teams bots, and eventually led to Microsoft acquiring the company. Peter spent years inside Microsoft shaping Copilot Studio, working on connectors that bridge the gap between APIs and real-world work. But the experience also gave him a healthy dose of perspective: he can show you slide decks from 2016 that promise the same things today’s AI pitches promise, always saying “within 5 years.” That pattern recognition shapes his practical, no-hype approach.

The 3,000 Scripts Experiment: Why AI-Last Beats AI-First

“At the end of the day, if I’ve been prompting all day, I should have a computer program that works offline, that works without a subscription. Otherwise, I didn’t really make anything.” Continue reading BONUS: From 3,000 Scripts to 3 Tools – Building AI-Last Software With Conversational AI Pioneer Peter Swimm

Efe Gümüs: The People-Pleasing Product Owner and the PO Who Understood User Value — Two Sides of Product Ownership

The Great Product Owner: The PO Who Understood User Value

“If your product owner can phrase what the user wants to do — not what the button should look like — it is going to be a night and day difference.” – Efe Gümüs

Efe describes the great product owner as someone who creates focus and a clear product vision, so the team knows what they’re building and why. The foundation is simple but powerful: describe what the user will be able to do, not what the interface should look like. Instead of specifying a red subscribe button with exact text in three languages, say “as a user, I want to subscribe to my favorite channel.” That shift unlocks the team’s ability to contribute design insights, architecture decisions, and user journey thinking — the kind of expertise no product owner could anticipate alone. Efe highlights the SPIDR slicing method as one of his favorite tools for breaking product backlog items into consumable pieces — by interface (iOS, Android, web), by data, by rules. When the PO frames work around user value and slices it effectively, the team delivers visible value in iterations, and sprint goals become meaningful. Without this, the team becomes a ticket delivery machine.

Self-reflection Question: When you look at your product backlog right now, are items described in terms of what users can do — or in terms of what the interface should look like?

The Bad Product Owner: The People-Pleasing PO Who Says Yes to Everything

“If you are doing everything your customer says, then you are not managing your product. That’s the foundation.” – Efe Gümüs

Efe names people-pleasing as the worst product owner anti-pattern — the “customer is always right” mentality applied to product management. When a PO says yes to every request, the consequences cascade quickly: multiple priorities competing simultaneously, everything marked urgent, no meaningful sprint goal, constant context switching, and new items injected mid-sprint.

The team loses focus entirely. Efe has seen this in startups where the CEO walks in with urgent customer requests, and in larger organizations where multiple customers each demand customizations. In both cases, the PO becomes a pass-through instead of a decision-maker. The customer might be happy today, but will they be satisfied in six months when nothing is coherent?

As Vasco notes, when you’re serving multiple customers and saying yes to one, you’re saying no to all the others — you just haven’t told them yet. The result is chaos: steering blindfolded without navigational tools, trying to go everywhere at the same time. A product owner’s most important skill is coherent, aligned decision-making — and that means learning to say no.

In this episode, we talk about Efe’s blog post on how to use Scrum in your hobby activities.

Self-reflection Question: How often does your product owner say no to stakeholder requests — and when they do say yes, is it because the request aligns with the product vision or because they want to avoid conflict?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!

About Efe Gümüs

Efe GümüsEfe is an out-of-the-box Agile Coach and Scrum Master who brings fresh perspectives to Agile by connecting it with everyday life. He uses metaphors to reveal mindset patterns and applies continuous feedback loops beyond work, including music production and gym training, constantly refining performance, creativity, and personal growth and resilience.

You can link with Efe Gümüs on LinkedIn.

Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Access three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Overcome Team Resistance and Gain Leadership Buy-In
Discover practical, real-world solutions from leading Agile practitioners. Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
FREE! Audiobook Chapters: Overcome Team Resistance and Gain Leadership Buy-In
Download three free chapters from 'Tips from the Trenches Scrum Master Edition' and start transforming your Agile practices today!
Your FREE ticket is on the way!
Check your inbox for details. Email us at ProductOwnerSummit.org if you have questions
Check Your Inbox For Details Email us if you have questions: ProductOwnerSummit@oikosofy.com
Your Ticket Is On The Way!