ownership Archives - Scrum Master Toolbox Podcast

Oluyomi Emmanuel: Creating Agile Value Stream Visibility Without More Administration

“Transparency is not created by displaying more information. Transparency is created when people share enough meaning to interpret that information in the same way.” – Oluyomi Emmanuel

Oluyomi’s current challenge is helping an organization create end-to-end visibility and ownership across several value streams without turning the solution into another layer of administration.

At first, the problem looked like a Jira hierarchy issue: initiatives, epics, stories, and tasks needed shared definitions. But the conversations exposed something deeper. Different groups used the same work item names to mean different things, and those differences made prioritization, dependency management, coordination, and reporting harder. Together with a colleague, Oluyomi framed the work as alignment experiments instead of a large rollout.

One workshop asked what makes an initiative different from an epic, what information must exist before work moves forward, and when the next level of work should be created. The biggest tension was ownership, not terminology. A second experiment, a cross-value-stream visibility session, used real initiatives to expose overlapping work, unclear ownership, and weak links to outcomes.

Vasco then pushed the conversation toward intake: perhaps the problem was not only shared meaning, but the absence of a single view of what the organization needs to do. Oluyomi’s next experiment is linking initiatives to quarterly goals and OKRs to see what really deserves attention.

In this episode, we refer to value streams, OKRs, and portfolio management.

Self-reflection Question: Does your organization have one visible list of important work, or many competing lists with unclear ownership?

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 Oluyomi Emmanuel

Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value.

You can link with Oluyomi Emmanuel on LinkedIn.

Oluyomi Emmanuel: From My Task to Our Work in Agile Teams

“We shifted their thinking from my task to our work.” – Oluyomi Emmanuel

Oluyomi describes a destructive pattern many Scrum Masters will recognize: local responsibility inside a supposedly shared team. The team looked collaborative during Scrum events, but once the meetings ended, developers, testers, and reviewers behaved like separate specialists. Developers finished coding and moved on. Testers waited for the right context or environment. Pull requests sat in review.

Everyone looked busy, and everyone could explain their own behavior, but work was not reaching Done. The board already showed the queues, yet visibility alone did not change behavior because the team still spoke in individual language: “my development is finished,” “testing belongs to QA,” and “my task is done.” The change started in a retrospective, where the team stopped asking who caused the delay and began asking where work stopped flowing.

They tested small experiments: swarming around items waiting in testing, reviewing aging work together, and avoiding new starts when existing work needed help. The daily standup became a place to ask a better question: what does this item still need before value can be delivered?

In this segment, we talk about flow, team ownership, and work in progress.

Self-reflection Question: What language in your daily standup reinforces “my task” instead of “our work”?

Featured Book of the Week: Handbook of Facilitative Leadership by Pepe Nummi

Oluyomi recommends Handbook of Facilitative Leadership: Concrete Ways to Boost Performance by Pepe Nummi. The book helped him see that leadership is not always about having the strongest opinion or offering the solution. Sometimes leadership means designing the process through which a group can think, contribute, decide, and take ownership together.

For Scrum Masters, that distinction matters because the people in the room often already have the knowledge needed to solve the problem. The knowledge is just distributed across the team. Facilitative leadership helps bring that knowledge into the open.

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

About Oluyomi Emmanuel

You can link with Oluyomi Emmanuel on LinkedIn.

BONUS: The Communication Tax — Why Your Team Collaborates Too Much and What to Cut First

In this BONUS episode, Roman Nikolaev challenges one of the most deeply held beliefs in the agile world: that more collaboration is always better. As Head of Technology at Cambri, Roman has watched teams burn their best hours in meetings and hand offs that create the feeling of productivity without the outcomes. He shares practical tools — from the vacation test to RFC processes — that help teams find the minimum viable level of collaboration.

From Senior Engineer to Accidental Manager

“I kind of accidentally ended up in management. I didn’t want to lead anyone, I wanted to be just a senior engineer doing my stuff. But somehow, four months in the job, I was already leading a team, and then one year after, I was head of technology.”

Roman’s career in engineering goes back to the early 2000s. When he changed jobs during COVID, he specifically didn’t want a management role — he wanted to code. But within months he was leading a team, and within a year he was running the entire technical organization at Cambri.

That unexpected shift from hands-on engineering to leading teams gave him a front-row seat to how collaboration actually works — and how often it doesn’t. What he noticed was that the most important differentiator for technical teams isn’t technical knowledge — it’s communication, and the tax you pay when communication goes wrong.

The Communication Tax Is Real

“The communication tax is real. The less we need to pay for communication, the more we can concentrate and own things end to end.” Continue reading BONUS: The Communication Tax — Why Your Team Collaborates Too Much and What to Cut First

BONUS: Why Delivery Breaks Down in Growing Tech Organizations—Ownership, Guardrails, and the People-First Company With Prashanth Tondapu

What actually slows down tech teams—lack of talent, or lack of ownership? In this episode, Prashanth Tondapu shares lessons from leading through global-scale failures, scaling from a small team to a 100-person company, and discovering why guardrails beat rigid processes when it comes to building teams that own outcomes and execute with discipline.

Diffusion of Accountability: When Everyone Is Responsible, Nobody Is

“Crisis is not the problem. Crisis is the one that uncovers the problem that has always existed.”

Early in his career, Prashanth witnessed a large-scale failure at a major technology company—not because the team lacked talent, but because accountability had become diffused. When too many people are responsible for something, it translates to nobody being responsible. The team was brilliant individually, but there was no clear demarcation of who owned what outcome. On good days, everything worked. But when things went wrong, there was no single person who could no longer delegate accountability to someone else. Prashanth connects this to the concept from Extreme Ownership by Jocko Willink—while the whole team must feel ownership, each individual needs laser-focused clarity on their specific accountability. As he frames it: outcome can only come with 100% emotional commitment to a particular problem, and when five people share that commitment, each carries only 20%. That’s where breakdowns happen.

The Leadership Design Problem: From Computers to People

“I was a developer who imagined that humans are also going to be as predictable as computers. Until 6 or 7 people, it works well because you can be everywhere. But as soon as we increased above 7, I was not able to be everywhere.” Continue reading BONUS: Why Delivery Breaks Down in Growing Tech Organizations—Ownership, Guardrails, and the People-First Company With Prashanth Tondapu

BONUS: Leadership Is Contextual — How a CTO Adapts From 7-Person Startups to 2,000-Person Organizations

In this CTO Series episode, Daniel Harcek shares how leading engineering teams across radically different scales — from a 7-person fintech startup to a 2,000-person cybersecurity company — taught him that leadership isn’t one-size-fits-all. We explore how he builds AI-first organizations, drives agile transformations, and why he believes every person in a company should think like a tech person.

What Works at 10 People Breaks at 100

“Leadership is contextual, not absolute. What works with 10 people breaks at 50, at 100.”

Daniel’s career spans from building a 30-person team for a German startup out of Žilina, Slovakia, to leading 70 engineers at Avast’s mobile division within a 2,000-person organization, and now running a 7-person team at WageNow. Each scale demanded a fundamentally different approach. At smaller scales, you strip away operational overhead and push ownership directly to the people. At larger scales, you need guardrails, dedicated roles, and structured processes that the smaller team would find suffocating. The lesson: don’t carry your playbook from one context to another — rebuild it for the reality you’re in.

End-to-End Ownership Replaces Specialized Roles

“Each engineer owns quality for the task he delivers. And he owns the fact that it comes to production.” Continue reading BONUS: Leadership Is Contextual — How a CTO Adapts From 7-Person Startups to 2,000-Person Organizations