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