Carmela Then Archives - Scrum Master Toolbox Podcast

Carmela Then: Why the Best Product Owners Let Go of What They’re Best At

The Great Product Owner: The Humble Leader Who Served His Team

“He was there, he was present, he was serving the team.” – Carmela Then

Carmela worked with a Product Owner at a bank who embodied everything servant leadership should look like. This wasn’t a PO who lorded his business expertise over the team—instead, he brought cookies, cracked jokes, and made everyone feel valued regardless of their role. He knew the product landscape intimately and participated in every refinement session, yet remained approachable and coachable.

When team members came to him confused about stakeholder requests, he willingly stepped in as a mediator. Perhaps most impressively, he actively worked to break down the hierarchical mindset that often plagues traditional organizations. In the beginning, testers felt they couldn’t question the business analyst or Product Owner.

By the end, QA team members were confidently pointing out missing scenarios and use cases—and the PO would respond with genuine appreciation: “Oh yes! We missed it! Let’s prioritize that story for the next sprint.” This PO understood that his role wasn’t to have all the answers, but to create an environment where anyone could contribute their expertise. The result was a truly flat, collaborative Scrum team operating exactly as Scrum was designed to work.

Self-reflection Question: How accessible are you to your team, and do you create an environment where anyone—regardless of role—feels comfortable challenging your thinking?

The Bad Product Owner: When Expertise Becomes a Barrier to Collaboration

Read the full Show Notes and search through the world’s largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

“He knows everything himself, and everything is in his head. So nobody else knows what he has in his head.” – Carmela Then

Carmela describes a Product Owner who wasn’t a bad person—in fact, he was incredibly capable. He knew the business from front to back, understood the systems intimately from years of analyst work, and could even write pseudocode himself. The problem? His very competence became a barrier to team collaboration.

Because he knew so much, he struggled to articulate his ideas to others. Frustrated that developers couldn’t read his mind, he started writing the code himself and handing it to developers with instructions to simply implement it. The result was disengaged developers who had no understanding of the bigger picture, and a PO who was drowning in work that wasn’t his to do.

Carmela approached this with humility, asking what she calls “dumb questions” and requesting that he draw things on paper so she could understand. She made excuses about her “bad memory” to create documentation that could be shared with the whole team.

Over multiple Program Increments, she gently coached him to trust his team: “You are one person. Please let the team help you. The developers are great at what they do—if you share what you’re trying to achieve, they can write code that’s more efficient and easier to maintain.” Eventually, he learned to let go of the coding and focus on what only he could do: sharing his deep business knowledge.

Self-reflection Question: As a leader, what tasks are you holding onto that you should be delegating—and what is your reluctance costing your team?

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 Carmela Then

Carmela is a Senior Business Analyst with 15+ years in financial and mining sectors. A Certified and Advanced ScrumMaster, she excels in leading agile initiatives, delivering business value, and aligning technical outcomes with strategic goals.

You can link with Carmela Then on LinkedIn.

Carmela Then: Why Teams Hate Agile (And How to Change That)

“They just hate it. They absolutely hate it. They had Agile fatigue.” – Carmela Then

Carmela describes what success looks like for a Scrum Master, and her answer might surprise you. Years ago, she might have pointed to metrics like cycle time. Today, she measures success by whether teams embrace Agile and Scrum rather than resent it.

She joined a team that was exhausted and bitter—their previous Scrum Master had been a micromanaging project manager in disguise. Stories were broken into disconnected tasks: one for development, one for testing, with no relationship between them. At the end of a sprint, nobody could answer whether something actually worked in production. The team hated Agile with a passion.

Carmela approached them differently—not as a threatening authority figure, but as a humble business analyst there to help. She let the Product Owner vent his frustrations about Agile in a retrospective.

Then, without preaching, she simply showed them another way: how to break down features properly, how to create end-to-end visibility, how to write stories that delivered actual value. Slowly, the team began to experience what Agile was meant to feel like. They stopped being “task deliverers” and started becoming value creators. The transformation wasn’t overnight, but the result was a team that finally understood—and even appreciated—why Agile works.

Self-reflection Question: If you asked your team whether they love or hate Agile, what would they say—and are you brave enough to ask?

Featured Retrospective Format for the Week: Emotional Seismograph

Carmela recommends the Emotional Seismograph as her go-to retrospective format. The setup is simple but powerful: create a graph with the sprint days on the horizontal axis and emotion levels on the vertical (happy at the top, sad at the bottom). Each team member draws a line showing how they felt throughout the sprint. The visual result is striking—and the conversations it triggers are invaluable. Carmela focuses on the extremes: moments of great happiness and moments of stress. She has team members add sticky notes to explain those peaks and valleys, allowing common themes to emerge. Her philosophy is that positive emotions drive productivity: “When the team is having a positive experience throughout their workday, they’re actually more productive. Stress is the silent killer—it makes people sick, takes them out physically and mentally, and people will just quit.” By putting a finger on the emotional pulse of the team, Scrum Masters can identify what to continue doing and what needs to change to lift the team into a better experience.

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

About Carmela Then

You can link with Carmela Then on LinkedIn.

Carmela Then: From Requirements Chaos to Story Mapping Success—How Planning Transforms Agile Teams

“We can’t continue to do this. Something has to change.” – Carmela Then

Carmela shares a story of organizational chaos that will resonate with many Agile practitioners. She joined a company where teams would jump straight into writing requirements without pausing to understand what they were trying to achieve. Vendor deliverables were thrown “over the fence” to internal technology teams with the assumption that everyone would magically know what to do. For almost a year, this pattern continued: teams writing stories on the fly while building, creating massive rework, confusion, and burnout.

The Product Owner faced constant stakeholder disappointment, having to explain what wasn’t delivered and why. Then came the breakthrough moment—the PO reached out and said, “We can’t continue to do this.” Carmela introduced a structured approach: workshops that brought business stakeholders and subject matter experts together to walk through end-to-end business processes. She implemented story mapping—visualizing the journey from beginning to end, with each major step broken into smaller, actionable stories.

Critically, she built in feedback loops: playback sessions where the team validated their understanding with stakeholders before committing to development. The result? Teams could now distinguish between well-understood work they could start immediately and the “hairy” items that needed more investigation. The Product Owner could make informed prioritization decisions, and the entire team gained visibility into the bigger picture.

Self-reflection Question: How often does your team pause to map the full end-to-end journey before diving into requirements, and what might you be missing by skipping this step?

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

About Carmela Then

You can link with Carmela Then on LinkedIn.

Carmela Then: When Remote Teams Stop Listening—The Silent Killer of Agile Collaboration

“Two minutes into it, my mind’s starting to wander and I started to do my own thing.” – Carmela Then

Carmela paints a vivid picture of a distributed team stretched across Sydney, New Zealand, India, and beyond—a team where communication had quietly become the enemy of progress. The warning signs were subtle at first: in meetings with 20 people on the call, only two or three would speak for the entire hour or two, with no visual aids, no PowerPoints, no drawings. The result? Within minutes, attention drifted, and everyone assumed someone else understood the message.

The speakers believed their ideas had landed; the listeners had already tuned out. This miscommunication compounded sprint after sprint until, just two months before go-live, the team was still discussing proof of concept. Trust eroded completely, and the Product Owner resorted to micromanagement—tracking developers by the hour, turning what was supposed to be an Agile team into a waterfall nightmare. Carmela points to a critical missing element: the Scrum Master had been assigned delivery management duties, leaving no one to address the communication dysfunction.

The lesson is clear—in remote, cross-cultural teams, you cannot simply talk your way through complex ideas; you need visual anchors, shared artifacts, and constant verification that understanding has truly been achieved.

In this segment, we talk about the importance of visual communication in remote teams and psychological safety.

Self-reflection Question: How do you verify that your message has truly landed with every team member, especially when working across time zones and cultures?

Featured Book of the Week: How to Win Friends and Influence People by Dale Carnegie

Carmela recommends How to Win Friends and Influence People by Dale Carnegie, a timeless classic that remains essential reading for every Scrum Master. As Carmela explains, “We work with people—customers are people, and our team, they are human beings as well. Whether we want it or not, we are leaders, we are coaches, and sometimes we could even be mentors.” Written during the Great Depression and predating software entirely, this book emphasizes that relationships and understanding people are the foundation of personal and professional success. Carmela was first introduced to the book by a successful person outside of work who advised her not just to read it once, but to revisit it every year. For Scrum Masters navigating team dynamics, stakeholder relationships, and the human side of Agile, Carnegie’s principles remain as relevant today as they were nearly a century ago.

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

About Carmela Then

You can link with Carmela Then on LinkedIn.

Carmela Then: The Scrum Master Who Learned That Perfect Boards Don’t Build Perfect Teams

“The failure part is, instead of leading the team to work toward a common vision, I was probably one of the persons that helped the divide.” – Carmela Then

Carmela shares a vulnerable story from her first Scrum Master role at a bank. Armed with training, certifications, and the ability to build a beautiful physical Scrum board with perfectly straight lines, she believed she was ready to lead. But Carmela quickly discovered a crucial truth: mastering the mechanics of Scrum is vastly different from serving a team’s real needs. Instead of showing up as a humble learner willing to grow alongside her team, she put on a facade of competence and confidence.

When two Product Owners began fighting for dominance, rather than stepping back and focusing the teams on their shared purpose, Carmela found herself drawn into the political battle, supporting one PO over the other. The result was devastating—a toxic environment where one PO was demoted, and talented team members left the organization entirely. Looking back, Carmela recognizes that her failure wasn’t about the Scrum board or ceremonies; it was about not putting the customer and common goals at the center. She learned that Scrum Masters must lead with humility, focus on outcomes rather than egos, and help teams unite rather than divide.

In this episode, we refer to John C. Maxwell and Failing Forward by John C. Maxwell.

Self-reflection Question: When was the last time you prioritized looking competent over truly serving your team’s needs, and what did that cost you?

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

About Carmela Then

You can link with Carmela Then on LinkedIn.