I’m really pleased to welcome Tomo Lennox to today’s conversation. Tomo brings deep experience helping teams figure out how to work smarter, not harder. With decades of experience in software delivery, project management and coaching, he’s worked with organizations of all sizes to improve how they deliver value.
What makes Tomo stand out is how grounded he is in the real world of work. He has helped countless teams bridge the gap between Scrum and Kanban. He challenges rigid frameworks and encourages teams to think critically about what actually fits their business context.
In our conversation, we explored one of the most common questions agile teams ask: When should you use Scrum, and when is Kanban a better fit?
The session is packed with examples, visual models and practical lessons that show how blending the two can lead to smoother workflows and more balanced teams.
We also had a quick Q&A session after, where Tomo and I dive deeper into topics like workflow efficiency, story sizing, forecasting, and how to keep your process truly human-centred.
The Truth About Idle Time and Flow
Many managers still believe that if people are not constantly busy, productivity must be slipping. Tomo Lennox loves to challenge that idea.
He tells a story that perfectly captures the problem.
A manager buys a baseball team. He looks out at the field and notices that half the players are just sitting on the bench. Frustrated, he shouts, “I am paying you to play, not to sit! Everyone get up and start throwing balls!”
Within minutes, the field turns into chaos. Balls are flying everywhere, no one knows what is happening, and the game completely falls apart.
Tomo laughs when he tells this story, but his point is sharp: “Sometimes idle is a good thing. You do not fix a bottleneck by keeping everyone busy.”
In Kanban, the goal is not to make sure every person is working at every moment. The goal is to make sure the right work is flowing. When a bottleneck appears, Kanban tells the team to shift their attention to where it is truly needed. That simple act of collaboration can lead to stronger relationships and faster progress overall.
Tomo explains, “Before you idle people, you move people. That is what Kanban teaches.”
Idle time is also where innovation starts. When there is a quiet moment with no urgent task, people can learn something new, improve a tool, or explore a better way to work. “Idle time is not wasted time,” Tomo says. “It is the space where learning, improvement, and creativity happen.”
In the end, it is not about doing less. It is about working smarter, finding the real rhythm of your team, and building a pace that people can sustain. As Tomo puts it, “Work should have a human rhythm. You do not need to sprint forever to get somewhere.”
The Power of the Board: Shifting Focus from People to Flow
One of the biggest traps teams fall into is turning their daily meetings into status updates. Everyone goes around the circle, saying what they did yesterday and what they plan to do today. The meeting ends, and nothing really changes.
Tomo Lennox has a better way. “When I act as a Scrum Master,” he says, “we do not talk about people, we talk about tasks.”
For him, the board whether it is Scrum or Kanban, is the single source of truth. It shows the real state of the work, not personal progress reports.
The focus shifts from individual updates to collective progress.
This simple change has a huge impact. Meetings become shorter, more meaningful, and energizing instead of repetitive. Teams stay aligned without micromanagement. And perhaps most importantly, people start collaborating instead of reporting.
Story Size and the Myth of Estimation
When the topic of story estimation came up, Tomo Lennox did not hesitate to share “I do not believe in story points, I believe in right-sizing.”
His approach is refreshingly simple. If a story feels too big to finish in a week, the team just splits it. And he has solid data to prove his point. After analyzing more than seventy thousand stories from a large organization, Tomo found almost no correlation between story points and how long the work actually took. “Estimation gives the illusion of precision,” he said, “but it does not make work more predictable.”
Instead of wasting time assigning points, Tomo encourages teams to ask smarter questions:
How many acceptance criteria does this story have? How many possible exit conditions could affect it?
These questions get straight to the heart of complexity and lead to better, faster planning.
The goal is not to measure everything; it is to understand the work well enough to move it forward.
Forecasting with Probability, Not Guesswork
Tomo Lennox is not a fan of guessing games. “Project managers have been doing estimation for decades, but most of it is just junk science.”
Instead of relying on gut feelings or point estimates, Tomo champions probabilistic forecasting, a data-driven way to predict delivery outcomes. “Rather than asking when something will be done, look at how your system actually behaves,” he explained. By modelling throughput and backlog trends, teams can forecast outcomes based on evidence, not opinion.
Using techniques like Monte Carlo simulation, a team might see that they have a 70 percent chance of finishing by a certain date. That data gives leaders options. They can accept the risk, change priorities, or adjust scope before it is too late.
“Probabilistic forecasting turns guessing into decision-making,” Tomo said. “It gives you real numbers to have real conversations.”
The result is clearer planning, earlier insights, and a healthier way to manage uncertainty. Teams can finally stop pretending they can predict the future and start working with it.
Looking Ahead: AI and the Future of Agile
As the conversation wrapped up, Tomo shared a glimpse into his newest project, RenJi. While Scrum and Kanban have served teams well for years, he believes a new era is emerging, one shaped by artificial intelligence.
“Agile was designed around humans,” Tomo pointed out. “All those ideas about limiting work in progress and avoiding overload make sense for people. But AI is different. It can handle many things at once.”
He imagines a future where AI continuously aligns work with strategy, automatically evaluating stories for cost, value, and impact. “What if an AI agent could look at your backlog, check which stories fit your strategy, estimate their cost based on past data, and even predict their potential revenue?” he asked. “Then, when you pull the next story, you already know it’s the best bet.”
He envisions AI not as a replacement for Agile, but as an extension of it, a way to connect strategy, flow, and delivery into one continuous system. “AI could help us do what Agile always promised, continuous learning, continuous delivery, and better decisions.”
He is still building RenJi and invites others to join him on this journey.
If Tomo’s ideas inspire you and you would like to be part of what comes next, get in touch at tomo@tomolennox.com and learn more about his newest venture, RanJi – an exciting step toward the future of Agile with AI.
I wish you a productive day, and I’ll see you next week, same time and place, for more managerial insights. Bye for now!
