Agile in the Enterprise - Lessons Learned in the Real World (VIDEO)

Happy New Year from the SSW TV team!

We’re kickstarting the year by releasing a video special. It’s an in-depth interview featuring a real life product owner who talks to us about his perspectives using Agile on a large scale Enterprise project.

SSW has just finished 28 weeks building the first release of a transport management system for a major Australian transport company. Join the Product Owner (client) and the lead developer as they hold a live retrospective reflecting on what went well and what could be improved.

The project was a time and materials engagement using scrum. This warts and all interview is your opportunity to get a behind the scenes look at the scrum process from the perspectives of a client and a developer. You will hear honest feedback of the pros and cons of scrum from both parties.

Adam Cogan, Chief Architect at SSW, hosts this interview and is joined by Keith Longworth, the Product Owner, and Gerard Beckerleg, the lead developer on the project.

During the interview each party will be asked:

How did the client choose the development company and what were the pros and cons of this approach
How accurate were the estimates compared to the actuals
What is your philosophy regarding estimates
What were the shortcomings of the Scrum Agile process
What were the benefits of scrum
Did the project finish on time and on budget? How does the business feel about the result?
If you had to start the project again, what would you change about the project?

Take the Quiz!

[WATUPRO 19]

About the speakers

Agile Pros

Keith Longworth has been involved with designing and building systems in the IT industry for the past 30 years. His career commenced in the 80's designing large systems for the NSW Police Department and for a global call centre.

He spent over 20 years many at Director level working for a large international logistics and transport company in both Australia and Asia building and implementing enterprise systems.

He brings a wealth of experience and talks about his latest work building systems for a major Australian transport company in conjunction with SSW using scrum and agile technologies.

Gerard Beckerleg is a Solution Architect at SSW in Sydney since 2011.

As a qualified Professional Scrum Developer, Gerard is capable of working as part of a Scrum Development Team or in the role of Scrum Master. His experience as a Scrum Master covers a wide range of clients and industries including McDonalds, Sydney Airports, National Australia Day Council and TAFE.

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. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

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!