EP17: Build Something Real
This episode is the full story of building a product as a non-engineer — 60 user stories, five planned releases, a real design handoff, and what 15 years of facilitating never taught. Take the Assessment | Watch on YouTube
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
This episode is the full story of building a product as a non-engineer — 60 user stories, five planned releases, a real design handoff, and what 15 years of facilitating never taught. Take the Assessment | Watch on YouTube
At Team '26, Atlassian shipped two tools that the agile community is not talking about. The Teamwork Graph CLI gives you 300 commands to manage Jira from your terminal. The MCP Server lets AI agents read and write to your Jira instance without a human in the loop. One removes the UI from your workflow. The other removes you from the workflow. This episode breaks down what these tools actually mean for agile careers, the Builder vs Orchestrator distinction, and three levels of response depending on where you are right now. Read the full breakdown: agiletactix.ai/blog/atlassian-just-proved-it Take the Agile AI Readiness Assessment: agiletactix.ai/assessment Agile AI Prompt Playbook: agiletactix.ai/blueprint
The Scrum Master and Product Owner weren't two separate stories. They were the first two chapters of the same story — and it's bigger than either role. In this episode, I walk through the role-by-role squeeze hitting Business Analysts, Project Managers, RTEs, and mid-level software engineers. Then I name what the enterprise is converging on: Orchestrator. In this episode: The execution layer AI is replacing across every knowledge work role Why the hourglass organization (PwC) makes generalists the most valuable Eightfold AI naming AI Orchestrator the most important job of 2026 Why the specialist who adds horizontal range becomes unstoppable The Jevons Paradox: more work, smaller middle Take the Assessment: agiletactix.ai/assessment Free Playbook: agiletactix.ai/blueprint
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.
Newsletter
Five episodes a week. Career strategy meets AI automation. Delivered to your inbox every Monday.