A Podcast by Danny Liu
Agile thinking meets AI automation. Whether you stay corporate or go indie, the same skill set gives you options.
Latest Episode
The Scrum Master is not the only role losing ground. In Part 2 of Scrum Devolution, I go after the Product Owner role. The squeeze is coming from both ends: leadership is taking product strategy back directly, and AI is eating the execution layer. Strategy goes up. Execution goes down. The middle collapses.
There's a pattern repeating across large enterprises right now, and it's being called "agile maturity." A Scrum Master gets asked to run more teams. The coaching budget disappears. The role gets merged, or streamlined, or quietly stops appearing on the org chart. Leadership calls it progress. Teams becoming self-sufficient. The framework doing what it was supposed to do. In this episode, I'm naming what's actually happening: Scrum Devolution. It's not AI. It's not the next layoff wave. It's a power shift — the authority that was delegated to the Scrum Master role being quietly redistributed to the team, to engineering management, and increasingly, to automation systems. And the rebranding trend ("Delivery Manager," "Flow Architect," "Strategic Change Lead") is accelerating it. Without the underlying capability shift, you've invited the question that's hardest to answer if your value lives in the meeting room: what does this person actually deliver? Key Takeaways The devolution is structural, not incidental. When orgs talk about agile maturity, they're often describing a deliberate redistribution of authority away from the SM role — not an upgrade of it. Rebranding without reskilling is a trap. A new title invites comparison to people who actually have those skills. That's a comparison most rebranders aren't ready for. The people accumulating influence right now built things. Automations that run without them, dashboards that answer questions before anyone asks, systems that outlive their presence on the team. The 14-day proof. After a Fortune 500 layoff, a new offer in 14 days — not because of certifications, but because every role left behind something tangible that still ran. The frame that matters. Stop asking "what should I retitle myself?" Start asking "what will still be running after I leave?" Take the free Agile AI Readiness Assessment to find your current archetype (Facilitator / Builder / Orchestrator) and get a concrete starting point. Read the blog version: Scrum Devolution: The Power Shift Happening Inside "Agile Maturity" More episodes + newsletter: careeroptional.ai Free Agile AI Prompt Playbook: agiletactix.ai/blueprint Career Optional helps mid-career agile professionals evolve from facilitators to AI-powered technical partners. New episodes weekly. I'm Danny Liu. This is Career Optional.
Note: This is the audio companion to a full screenshare walkthrough video. For the best experience, watch the video on YouTube. A dedicated Claude Design deep-dive episode is coming soon. Claude Design just mass-launched and I used it to build a full website in under 25 minutes. No Figma. No design agency. No templates. In this walkthrough, I take Claude Design from zero to a complete, branded website — live on screen, no cuts, no fake demos. You'll hear exactly what it can do, where it breaks, and whether it's actually ready to replace a design team. Links: Take the AI Readiness Assessment Free AI Prompt Playbook Subscribe on YouTube
Jack Dorsey and Roelof Botha published "From Hierarchy to Intelligence" — an essay describing a future where AI replaces the context-carrying function of management. Block, the company behind Square and Cash App, laid off 40% of its workforce and restructured around three roles: individual contributors, directly responsible individuals, and player-coaches. Meanwhile, the agile community is quietly rebranding the Scrum Master role. Delivery Manager. Flow Architect. Strategic Change Agent. Same work, new labels. (It's the same move 3Back LLC tried in 2017 with their "Scrum 3.0" white paper. It didn't catch on then either.) One side says your role is eliminated. The other says it's promoted. Danny walks through why both are partially right, and the one question that cuts through the entire debate: What would break if you disappeared for two weeks? In this episode: Why Dorsey's "intelligence layer" argument is technically right Where the Block model breaks for Fortune 500 environments The 2017 Scrum 3.0 paper nobody remembers (and why today's rebranding looks identical) The difference between facilitation and building — and why only one survives A two-bucket audit every agile professional should run this week The future of your career isn't decided by an org chart. It's decided by what you can build. 🎧 More episodes + newsletter: careeroptional.ai 📘 Free Agile AI Prompt Playbook: agiletactix.ai/blueprint "Career Optional" helps mid-career agile professionals evolve from facilitators to AI-powered technical partners. New episodes weekly. I'm Danny Liu. This is Career Optional.
Every Monday morning, someone opens the Jira board and says "we're on track." Every other Friday, that same team misses the sprint commitment. The board is lying to you. And it's lying because the board only shows what people remembered to update. In this episode, I break down the difference between status and signal, and walk through a simple Jira automation rule I built at a Fortune 500 engagement. If a ticket hasn't had a status change or comment in 48 hours, it gets flagged, the team gets notified, and problems surface 2-3 days earlier. No AI. No custom app. Just smart JQL and two hours of setup. Links: Free Agile AI Prompt Playbook: agiletactix.ai/blueprint Show website: careeroptional.ai YouTube: Watch on YouTube
Newsletter
Five episodes a week. Career strategy meets AI automation. Delivered to your inbox every Monday.