Author Archives: Steven Thomas

About Steven Thomas

Steven Thomas an independent Agile Programme Manager.

Value Creation: The Engine Behind Sustainable Growth

Posted on by
Reply

Private equity firms live and breathe value creation — it’s how they make their money. But they’re not the only ones who should care. Every business leader should be thinking about value creation. Yet, surprisingly, many aren’t.

So what is it? Why does it matter? The short answer: the most successful businesses understand how to build, scale, and sustain growth by deliberately creating value — for customers, employees, shareholders, and more. If you’re not focused on it, you’re leaving opportunity (and probably money) on the table.
Continue reading →

AI Isn’t Magic — It’s a Stack

Posted on by

Artificial Intelligence. Two words that trigger everything from excited coffee chats with my mates to boardroom FOMO to outright apocalyptic fear. AI has dominated every conversation I’ve had for the last six months. Everyone wants a slice of it. It shows up in product roadmaps, vendor decks, job specs, and shareholder updates. But when I scratched beneath the surface, I found a messy pile of buzzwords and vague ambition.

I don’t know about you, but I like simple. So here is my attempt to make AI simple.

If you’re leading digital delivery, managing platforms, or just trying to figure out what AI means for your portfolio, this is your practical intro. There are buzzwords, but I explain them. There is no hype because I don’t have to impress anybody. It is just a clear look at how AI is structured, what matters now, and what’s coming.

Continue reading →

Bold Predictions or Hype? Tech CEOs on AI’s Impact on Software Development

Posted on by

I’ve never seen a hype cycle like this one. Huge sound bites about AI — specifically, generative AI. Depending on who you ask, AI is either a helpful copilot or it’s gunning for your entire dev team’s jobs. As usual the truth is probably somewhere in between. But with so many CEOs talking up how much code AI is generating, it’s worth stepping back to ask: are they predicting the future, or selling it?
Continue reading →

Another Silver Bullet? What AI Tools Can Learn from the Last 50 Years of Developer Hype

Posted on by

The emergence of AI coding assistants such as GitHub Copilot, Amazon CodeWhisperer, and Claude 3.5 Sonnet has stirred debate about their long-term impact on software development. I’ve been in this game a while, which means I approach software innovation with a healthy dose of scepticism. I have seen lots of fashion trends — waves of developer productivity tools — some impactful, most not. From 4GLs to IDEs to low-code — each one promising to change the game, then fading into the background. Sound familiar? Every year there is somebody claiming they have a tool that can write your code for you. Is AI just the latest wave? I wondered if looking back at those old patterns — the hype, the crashes, the survivors — might tell us where this one’s going. Do those patterns from history tell me anything about the current trajectory of AI coding tools? The answer? Yes and no. Which, if you’ve ever worked in software, is probably the only honest answer you’ll get.
Continue reading →

What Software Development Can Learn from Double-Entry Bookkeeping

Posted on by

Double-entry bookkeeping revolutionised business by introducing a self-checking system of financial integrity. In the world of software, Behaviour-Driven Development (BDD) does something strikingly similar — pairing each feature with a clear, testable description of how it should behave. Double-entry bookkeeping and automated software testing might seem worlds apart – one emerged in Renaissance-era accounting and the other in modern software development. Yet conceptually, they serve a similar purpose: both introduce systems of checks and balances to ensure integrity and accuracy in their respective domains. In accounting, double-entry bookkeeping requires every transaction to be recorded in two accounts (debits and credits) that must balance, creating an internal self-checking mechanism. In software, automated tests act as a parallel record of expected behaviour, continuously verifying that the code produces the intended outcomes. This post explores how a 500-year-old accounting innovation revolutionised financial record-keeping and how its spirit lives on in the way we write and test software today.

Continue reading →

Disaster, rescue and recovery: Kickstarting delivery

Posted on by

70% of projects fail to deliver — and the cost is more than financial. Few broken programmes crash in a spectacular fashion. Most just quietly stall. You’ve got a roadmap. You’ve got people. You’ve got the rituals. But… nothing’s really moving. Instead you have sceptical stakeholders, wincing delivery teams, endless meetings and no actual decisions. Everyone is busy, but no one is sure what they’re delivering or why. Sound familiar? You’ve stalled.
Continue reading →

Choosing the Right Nearshoring Location: 9 Essential Criteria

Posted on by

I’m based in London, UK, but I’ve had teams in South America, USA, Eastern Europe, the Middle East, South Africa, and India. Some of those locations worked for me and some didn’t.

In 2017 I opened a software development operation in Sofia (Bulgaria) for one of the world’s leading news organisations, headquartered in London (UK). Sofia met our criteria for selecting a nearshore location (and still does). I thought others might be interested in the nine criteria we used to select a nearshoring location. Particularly since I’ve inherited teams in other locations that did not meet these criteria.
Continue reading →

No Strategy, No Future: Why Companies That Drift, Sink

Posted on by

I was talking to my mate Ed the other day. It was one of those lets talk about anything conversations. We both have extensive consulting experience so perhaps it isn’t too surprising that we ended up talking about organisational strategy. Or the lack of it. A surprisingly high percentage of companies we have encountered lack an defined organisation strategy beyond “keep doing what we’re doing and hope”. Personally, I believe every company, regardless of size or industry, needs a strategy. Here’s why.
Continue reading →