Podcast Archives - Page 2 of 649 - 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.

Oluyomi Emmanuel: When Agile Team Trust Breaks Before the Scrum Master Acts

“Once that trust is broken, everything else, nothing else matters.” – Oluyomi Emmanuel

Oluyomi Emmanuel started his Scrum Master journey after a strategic move toward Agile ways of working changed his project coordinator role into something deeper: helping people communicate when the answers were unclear. In this episode, he shares a hard lesson from a newly formed software team of eight people, where tension between a tech lead and a new developer first appeared in GitHub pull request comments.

There were sarcastic replies, cameras switched off during the daily standup, and a growing distance when the team worked in the same office. Oluyomi initially treated it as a normal forming-stage conflict and waited for the team environment to absorb the tension.

By the time the tech lead escalated concerns to the developer’s line manager, trust had already deteriorated. A facilitated feedback session produced an improvement plan, but the developer experienced the feedback as judgment rather than support and left the team less than a month later. Oluyomi’s lesson was clear: a Scrum Master needs to name trust concerns early, first in one-on-ones, then together, before the relationship becomes too damaged to repair.

In this episode, we refer to psychological safety, conflict resolution, and team trust.

Self-reflection Question: What early sign of broken trust have you noticed but not yet named with your team?

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: Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani

AI is changing the work of software teams, but Salima Bhimani argues that the bigger question is not only what AI can automate. In this BONUS episode, Salima shares what she learned inside Alphabet’s moonshot ecosystem, why breakthrough ideas may be hiding in plain sight, and how more people can become moonshot makers when technology meets lived intelligence.

To know more about her work, check out her latest book, Invent Now: The Next Leap in Moonshots and her website.

Invention Starts in Real-World Constraints

“Invention is something that is always happening in relationship to something that’s in the world.”

Salima traces her view of invention back to a family history of migration, adaptation, and rebuilding under constraints. Her roots go from India to East Africa, where her family had to learn new languages, new land, and new ways to survive. That experience shaped a practical view of innovation: invention is not only the work of a lone genius in a lab. It often starts in friction, necessity, and the daily encounter between people and the systems around them.

We May Be Thinking Too Small About Innovation

“We’ve actually shrunk our ability to see what’s out there in the world by limiting who’s in the room.” Continue reading BONUS: Why AI Needs More Than Silicon Valley Moonshots With Salima Bhimani

Pankaj Kumar: Product Owners Who Prepare the Ground for Agile Teams

The Great Product Owner: Proactive Preparation Before the Team Asks

“Before the team asks, you know that this is the prerequisite for this user story.” – Pankaj Kumar

Pankaj’s example of a great Product Owner is someone who did the homework before meeting the team. This PO understood what the team needed to deliver, prepared the acceptance criteria, talked to UX early, and made sure design inputs were available before developers were blocked.

Vasco describes this as “preparing the ground” for the team. The PO was not just pushing features into a sprint. He was listening to what the team could achieve, translating stakeholder needs into clearer work, and reducing waiting time so the team could focus on execution.

For Scrum Masters, this is a useful pattern to notice: great Product Owners protect the team’s flow by handling communication and dependency work early.

Self-reflection Question: What does your Product Owner prepare before the team discovers it needs help?

The Bad Product Owner: Pushing Urgent Work Into an Already Full Sprint

“The team was already having everything on the plate, and they can’t take any more.” – Pankaj Kumar

The anti-pattern Pankaj highlights is a Product Owner who treats urgency as permission to ignore capacity. In one sprint, a PO arrived with an important customer case and insisted that it had to enter the current sprint backlog. The team was already overloaded, but the PO was not ready to hear the tradeoff. Pankaj’s advice is to slow the conversation enough to make the real decision visible.

Why is this urgent?

Who is the stakeholder?

What is the risk?

What is the impact?

Can it wait until the next sprint? If it cannot wait, what will be adjusted?

Agile welcomes change, but change still has a cost. A Product Owner who says yes without making the tradeoff visible risks damaging trust with the team.

Self-reflection Question: When urgent work enters the sprint, what does your team explicitly remove or renegotiate?

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

About Pankaj Kumar

Pankaj Kumar is an experienced Scrum Master and Agile Coach with over 18 years in IT. He helps teams adopt Agile ways of working, improve collaboration, remove impediments, and deliver value consistently. He facilitates Scrum ceremonies, coaches teams and stakeholders, and supports Agile transformation across organizations.

You can link with Pankaj Kumar on LinkedIn.