📞 Contact us: https://bit.ly/4fAFrVx

In this session, Eli Kent, Software Engineer II and Scrum Master at SSW, demonstrates how AI agents are transforming the Scrum process by automating backlog refinement, daily Scrum preparation, and sprint reviews. Working on TinaCMS, Eli faced a backlog of 300 Product Backlog Items (PBIs) requiring triage. By introducing agentic workflows powered by Claude Code, GitHub Actions, and AI models, he reduced that number to just 9.

Eli walks through his practical approach to becoming an Agentic Scrum Master, showing how AI agents can manage repetitive tasks while keeping human oversight and approval at the centre of the process. Eli also explores the future of Scrum, where AI agents facilitate much of the process, product owners set the direction, and developers spend less time managing administration. Whether you’re a Scrum Master, software engineer, product owner, or Agile practitioner, this session offers practical ideas for incorporating AI agents into your everyday workflows. The key takeaway: AI agents do the busywork. Humans stay in control.

00:00 | Introduction: Becoming an Agentic Scrum Master
02:14 | How AI Agents Reduce Scrum Master Busywork
05:28 | Agentic Workflows: Skills, Routines, Connectors and Guardrails
07:51 | AI Sprint Planning and the Definition of Ready
10:17 | System 1 vs System 2 AI Models for Backlog Triage
14:27 | Automating PBI Refinement with Claude Code and Parallel Agents
17:34 | Reviewing and Approving AI-Generated Backlog Changes
20:14 | Automating Daily Scrum Preparation and Team Capacity Tracking
23:28 | AI-Powered Sprint Reviews with Claude Code and TinaCMS
28:35 | The Future of Agentic Scrum, Key Takeaways and Q&A

🌐 About SSW: https://linktr.ee/SSWTV

🔗  Links:

LinkedIn: https://linkedin.com/company/ssw

Twitter: https://twitter.com/ssw_tv

Facebook: https://facebook.com/SSW.page

Instagram: https://instagram.com/ssw_tv

Tiktok: https://www.tiktok.com/@ssw_tv

👋 Get in touch:
Eli Kent – SSW Software Engineer II
About: https://www.ssw.com.au/people/eli-kent
LinkedIn:   / ekent  

#AgenticAI#ScrumMaster#AIAgents#ClaudeCode#Scrum#Agile#SprintPlanning#GitHubCopilot#TinaCMS#Automation#ArtificialIntelligence#SoftwareDevelopment#SSW#SSWTV

V1 – Bahjat

About the speakers

About the speakers

Eli Kent

Eli is a Melbourne-based Software Engineer originally from Invercargill, New Zealand. He specialises in building scalable, maintainable software using modern Microsoft and JavaScript technologies. At SSW, he works with clients across industries to deliver clean, cloud-first solutions that balance performance, usability, and long-term maintainability.

Related videos

Related videos

Vibe Coding is fast, but is it Enterprise Ready? | Adam Cogan | SSW Rules

Vibe coding is transforming software development, allowing developers to build features in minutes instead of days. But does faster coding mean better software?

In this SSW TV episode, Adam Cogan explores the excitement and hidden challenges of AI-powered development. Using a Formula 1 analogy, he explains why speed alone isn’t enough when navigating the complexities of architecture, security, testing, and maintainability.

Discover how enterprise vibe coding, or AI-assisted engineering, combines the speed of AI with the right architecture, context, and guardrails to build reliable, maintainable software.

🚀 Enjoy the speed, but don’t forget the corners!

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!