The Great Product Owner: Open Communication, Active Listening, and Feasibility First
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.
"Start the open conversation and listen to the critical discussions." - Kaloyan Chalakov
Kaloyan describes the best Product Owner pattern as almost the opposite of control. A strong Product Owner comes to the team with the outcome, the timeline, and the stakeholder context, then starts a feasibility conversation. They ask what is possible, what is risky, what can be decomposed, and what the team needs in order to deliver. In Kaloyan's example, the Product Owner stayed focused on stakeholder communication while the team helped shape the work into something practical. Stakeholders were kept in the loop, risks were visible, and everyone could adjust plans early. The most useful behavior was not a personality trait, because every Product Owner is different. It was open communication and active listening, especially when the team raised uncomfortable technical or delivery constraints. Great Product Owners do not need the team to say yes to everything. They need the team to help them face reality early enough to make better product decisions.
Self-reflection Question: How often do your Product Owner conversations start with feasibility and shared reality, rather than commitment pressure?
The Bad Product Owner: Acting Like the Boss of the Team
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.
"Tell me what exactly to do, and I'll do exactly what you're telling me to do." - Kaloyan Chalakov
The Product Owner anti-pattern Kaloyan warns us about is the Product Owner as the boss of the team. This shows up when the Product Owner assigns work, manages people, and controls every detail of delivery instead of focusing on product outcomes and customer needs. The consequence is a damaging loop. The team stops bringing their thinking and creativity, waits for instructions, and becomes task handlers. The Product Owner then feels overwhelmed because every decision and question returns to them, so they add more control. That control removes even more initiative from the team. Kaloyan connects this pattern to the Product Owner's real work: difficult conversations with customers, narrowing big requests into practical steps, and protecting focus on product value. When the Product Owner becomes the team's manager, both product discovery and team self-organization suffer.
Self-reflection Question: Where might your Product Owner role be taking decisions away from the team instead of creating clarity for better decisions?
[The Scrum Master Toolbox Podcast Recommends]
🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥
Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people.
🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.
Kaloyan Chalakov spent years making high-stakes decisions at sea before moving into Agile and organisational change, bringing lessons from safety-critical systems into how modern teams work.
Surprise, it's me. I thought I'd share what I've learned in my 17 years as a newspaper columnist for both local and national titles, including my advice for getting started and getting your next commission.
Hi everyone! It’s been a busy few weeks since my last roundup: the Shipaton 2026 winners are in, and three Kotlin Multiplatform apps took the Ship Kotlin Everywhere Award. In other news, Kotlin 2.5.0 is taking shape with its second Beta, KotlinConf 2027 is officially heading to Kraków with the call for speakers open, and the new State of Kotlin in 2026 report shows where the language stands after 15 years. Here’s what stood out to me most:
Kodee-approved spotlight
Ship Kotlin Everywhere winners at RevenueCat Shipaton 2026
Out of 3,985 Shipaton submissions, three standout projects took home JetBrains’ Ship Kotlin Everywhere awards. What caught my eye is that the same Kotlin Multiplatform and Compose Multiplatform toolkit yielded three completely different results.
🥇 BoatBrawl by Rehaan Cubes and Ashwin K M
🥈 AfterFade by Kanon Fujita
🥉 Lumeo by Piotr Prus
A huge congratulations to the winners, and to everyone who shipped an app. I’m off to start a new project of my own!
Start your next KMP app with Kotlin Toolchain 0.13
Kotlin Toolchain 0.13 brings `kotlin new` for interactive project creation, smoother iOS setup, SwiftPM dependency support, and faster Kotlin/Native rebuilds. We recommend it for most new KMP projects. Give it a try!
Kotlin turned 15 this year, and the new report offers a fascinating look at how the ecosystem has grown. More than half of Kotlin developers report working on backend projects. Among surveyed Kotlin developers, 93% use at least one AI coding tool, and 81% say AI-generated Kotlin code is fully correct or requires only minor fixes. What surprised you most?
Save the dates! KotlinConf 2027 is heading to Kraków, Poland, April 21–23. April 21 is workshop day, followed by two conference days. Have an experience, tool, or Kotlin lesson worth sharing? The call for speakers is open, with submissions due November 27. I’d love to see you on stage or somewhere in the audience!
The Kotlin Multiplatform Contest is open: Win a trip to KotlinConf
Students and recent graduates, turn your idea into a cross-platform project with Kotlin Multiplatform!
The authors of the top three projects will each win a trip to KotlinConf 2027 in Kraków, Poland. Authors of all other valid entries will receive Kotlin souvenirs. Submissions are open until December 7, 2026.
Kotlin 2.5.0-Beta2 landed on October 21. It brings stable name-based destructuring in only-syntax mode, an unused return value checker, Java 28 support, and Swift export in Beta with a new DSL. Kotlin/Native incremental compilation is also now enabled by default on Apple targets. Prefer a maintenance release? Kotlin 2.4.21 arrived in October with bug fixes.
The minimum JDK version required to run the Kotlin compiler is changing. In Kotlin 2.5.0-Beta1, running the compiler on a JDK older than 17 triggers a warning. In Kotlin 2.5.0-Beta2 and 2.5.0, it triggers an error, with a flag to temporarily continue using an older JDK. Starting with Kotlin 2.5.20-Beta1, JDK 17 or newer is required. If your machines or CI still use an older JDK, now is a good time to upgrade.
Looking for the right libraries for your next multiplatform app? On Klibs.io, you can compare Voyager, Decompose, and Circuit for Compose Multiplatform navigation. Or try Ktorfit to describe HTTP APIs with a familiar Retrofit-style interface while using Ktor under the hood. You can also let your AI agent do the checking – the Klibs.io MCP server gives it direct access to the multiplatform library catalog.
Ryan is joined by Charity Majors, co-founder and CTO at Honeycomb, for a conversation about applying the concept of immutable infrastructure to software development to treat code like cattle instead of pets, shifting the paradigm of system specifications to accommodate the rapid influx of AI-generated code, and navigating the complex ethical boundaries between system observability and human surveillance in modern technology ecosystems.
Log in
