Baldur's Gate 3: How Larian Studios Accidentally Schooled the Agile Zealots

In the sprawling, jargon-infested world of software development, "Agile" is the buzzword that just won't die. It's the sacred cow that companies love to name-drop at meetings, all while missing the point entirely. Yet along comes Larian Studios with Baldur's Gate 3, and whether they meant to or not, they've just shown up 90 per cent of the so-called Agile practitioners. Yes, the same ones who plaster their walls with motivational posters and think stand-up meetings are a personality trait.

Let's be clear: Larian Studios may not have set out with the express intention of being the poster child for Agile development. But in an industry where lip service is often paid more than actual service, they've managed to embody the very principles that most companies butcher in practice.

Check out this video for more of the scoop: https://www.youtube.com/watch?v=PEUbDy5gNbU

As Upton Sinclair reminds us, "It is difficult to get a man to understand something when his salary depends on his not understanding it."

Early Access Done Right—or How to Actually Listen to Your Customers

Remember when Early Access was a dirty term, synonymous with half-baked games and broken promises? Larian turned that on its head. By releasing Baldur's Gate 3 into Early Access back in 2020, they didn't just toss a bone to the masses; they opened a dialogue. They iterated based on actual player feedback—imagine that! While other companies were busy patting themselves on the back for pushing out MVPs (Minimum Viable Products, for the uninitiated), Larian was engaging in genuine, iterative development cycles.

Adaptability Over Rigidity—A Shocking Concept

Agile preaches adaptability, but too often, firms are as flexible as reinforced concrete. Larian, on the other hand, took adaptability to heart. Faced with critiques about buggy launches and story gripes, they didn't double down or gaslight their user base. No, they rolled up their sleeves and reworked fundamental pieces of the game. They embraced change, even when it meant more work—a concept that seems utterly alien to many Agile-in-name-only organisations.

Cross-Functional Collaboration Without the Corporate Claptrap

We've all sat through those mind-numbing meetings where "cross-functional collaboration" is discussed ad nauseam, yet nothing actually happens. Larian's team of developers, writers, and voice actors continuously refined the game, often returning to the recording studio to rework dialogue. They weren't siloed in their little kingdoms; they actually talked to each other and, shock horror, worked together effectively.

People Over Processes—Who'd Have Thought?

Agile's first value is "Individuals and interactions over processes and tools." But in many companies, employees are treated like cogs in a machine that's perpetually on fire. Larian bucked this trend by prioritising their team's well-being. Swen Vincke, the game director, spoke about maintaining their "developer joy." They even chose not to rush into a sequel or DLCs, opting instead to keep their team sane and creative. It's almost as if happy people produce better work—who could have guessed?

Delivering Value Continuously Without Making It a Hollow Mantra

Continuous delivery is another Agile staple that's often talked about but rarely executed well. Larian didn't just deliver updates; they delivered meaningful improvements. Each patch wasn't a token gesture but a substantial enhancement based on community feedback. They managed to keep players engaged over a three-year Early Access period, which is more than can be said for games that lose their player base three months post-launch.

Community Engagement That's More Than Skin Deep

While other companies treat community engagement as a box-ticking exercise—cue the occasional Reddit AMA and a Twitter giveaway—Larian's team, including the voice actors, actively engaged with the fanbase. They didn't hide behind corporate statements but embraced the memes, the fan art, and yes, even the thirsty tweets. They built a community that's invested, not just a customer base that's tolerated.

Learning from Mistakes Instead of Rebranding Them as 'Features'

In the software world, there's a nasty habit of rebranding bugs as "undocumented features." Larian took the high road. They acknowledged their missteps and, more importantly, learned from them. Vincke himself admitted to nitpicking aspects of the game even after its monumental success. The team is committed to not repeating past mistakes—a far cry from the cyclical blunders we see in other AAA studios.

So, What’s the Excuse of the Agile Purists?

If a game studio can organically embody Agile principles without making a song and dance about it, what's stopping the self-proclaimed Agile experts? Perhaps it's time to admit that slapping post-it notes on a wall and having daily stand-ups doesn't make you Agile. It's the mindset, the willingness to adapt, to collaborate genuinely, and to value people over processes.

The Ironic Twist

The delicious irony is that while companies are busy sending their staff to Agile training sessions and hiring overpriced consultants to implement frameworks they don’t even want to understand, Larian Studios just went ahead and did it. No fanfare, no sanctimonious lectures—just results.

As Upton Sinclair reminds us, "It is difficult to get a man to understand something when his salary depends on his not understanding it."

In Conclusion: Actions Speak Louder Than Buzzwords

Whether Larian intended to use Agile methodologies or not, they've out-Agiled 90 per cent of those waving the Agile flag. Baldur's Gate 3 isn't just a triumph in gaming; it's a masterclass in how to deliver a product that resonates with its audience through genuine Agile practices. So maybe, just maybe, it's time for the Agile evangelists to take a leaf out of Larian's book—less posturing, more doing.

Because at the end of the day, it's not about how Agile you say you are; it's about how Agile you actually are.