DOP 310: The Misconceptions and Realities of DevOps, Agile, and Leadership

Episode 310

Show Notes

#310: In this episode, Darin and Viktor sit down with Tim Beattie, co-founder and CEO of Stellafai, to chat about the myths and realities of DevOps and Agile in today’s workplaces. They dive into how DevOps and Agile should be seen more as philosophies rather than just titles on a business card. Tim shares his take on why roles like DevOps Engineer can actually create more silos and how the real goal should be about breaking down those barriers. They also talk about the crucial role of leadership in fostering a safe environment where teams can speak up and innovate. With references to aerospace and software industries, they show how adaptive practices are super important for staying relevant.

Frequently Asked Questions

Should DevOps be a job title?

Tim Beattie answers no on DevOps Paradox episode 310. Agile and DevOps are philosophies meant to bring silos down, so a DevOps engineer or a DevOps team creates exactly the thing they were supposed to remove: a pocket where DevOps lives and where every question about it gets sent. He accepts coach as a title, and treats those roles on a job listing as a warning sign.

Why was there never a waterfall coach?

Tim Beattie points out on DevOps Paradox episode 310 that waterfall had its own bodies, certifications and tooling, but it is methodical and top down, closer to following a recipe. Agile and DevOps instead try to produce self-organising and self-correcting teams, which needs facilitation. Viktor Farcic adds that waterfall never contradicted how managers already managed anything else, so it required no conversion.

Should teams follow Agile frameworks exactly?

Tim Beattie describes frameworks on DevOps Paradox episode 310 as guardrails: worth following closely for a month or two with an immature team, because there is good thinking in them. The sign of a maturing team is when it starts asking why a retrospective waits two weeks, or why a finished feature waits for the end of a sprint. Viktor Farcic argues that following a method to the letter contradicts the point of it.

What is the definition of done?

Viktor Farcic says on DevOps Paradox episode 310 that in years of asking teams, he never once heard the answer he wanted: running in production successfully. Tim Beattie goes further and adds being used and adopted. Farcic’s criticism of Agile in practice is that teams declared victory at the last commit while forgetting deployment, operation and observation existed at all.

Is DevSecOps a useful term?

Both guests on DevOps Paradox episode 310 dismiss it. Tim Beattie wrote a post objecting to the escalating variants and took criticism for it, arguing the philosophy already covers everything between having users and those users getting value. Viktor Farcic is blunter: if security matters, security is part of the chain already, and naming it separately produces one more silo rather than one fewer.

Does a rigid process make safety-critical software safer?

Tim Beattie reframes the question on DevOps Paradox episode 310. Looking at the disasters he has studied, the failure was a lack of safety at team and individual level: the people building the technology could see the problems and had no standing to challenge, say no, or ask for time. Top-down pressure and a rigid plan removed that, and the missing safety ended up in the product.

What is the DevOps Paradox podcast?

DevOps Paradox is a weekly podcast co-hosted by Darin Pope and Viktor Farcic, covering DevOps, platform engineering, and modern software delivery. Episode 310 brings in Tim Beattie of Stellify, previously global head of product for Red Hat Open Innovation Labs, to argue about job titles, framework orthodoxy, what done means, and where safety actually comes from. Every episode page carries the audio, the video, and a full transcript.

Episode Transcript

Read the Full Transcript

Topics

Share and Download

Guests

Tim Beattie

Tim Beattie

Tim Beattie is on a mission to empower teams to dream bigger, achieve more, and break the boundaries of what’s possible. As the CEO and co-founder of Stellafai, a strategy execution toolkit for goal-oriented teams who want access to world class coaches in their pocket, Tim is passionate about transforming how goal-oriented teams move from simply tracking tasks to truly executing strategy.

Hosts

Darin Pope

Darin Pope

Viktor Farcic

Viktor Farcic

Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.

His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).

He often speaks at community gatherings and conferences.

He has published DevOps Paradox and Test-Driven Java Development.

His random thoughts and tutorials can be found in his blog The DevOps Toolkit.