Latest posts
-
Bridging the Gap: The Strategic Value of a Technical Product Manager in a Sales-Focused Organisation
In many sales-led product organisations, particularly those that have evolved organically or have prioritised growth through customer acquisition and commercial opportunity, the role of the Technical Product Manager (TPM) can often be underappreciated, if not entirely absent. However, as product portfolios mature, architectures grow more complex, and customer expectations trend ever upward, the need for…
-
A good plan for the future can make or break your Technical Due Diligence
When private equity firms evaluate a company for investment, understanding the company’s future plans is a vital part of the Technical Due Diligence (TDD) process. Investors are not just interested in the present state of the company but regard both the future plans, and the structure that surrounds them, as critical parts of the investment…
-
Just what is Technical Debt?
Technical debt refers to the additional work and future costs that arise when a company opts for a quick, easy solution now instead of a more efficient and long-term approach. It’s like taking a shortcut that saves time initially but requires more effort to fix later. Technical debt can accumulate in various forms, such as…
-
It’s all about the velocity isn’t it?
In a word, no. Velocity has been a core metric for Scrum based projects since its inception in 1995. Organisations like it because it’s a quantifiable figure, and one that can be measured over time. But it has problems, it has a lot of problems. “Then you should say what you mean,” the March Hare…
-
Unpicking spaghetti
Why is software governance complex? We’ve talked about the three gates of software development and why organisations make this more complex, but why is it more complex? Why can’t we fix it? Understand the complexity The first reason things become complex in organisations is “scale”. Simply put, while a startup might be able to concentrate all…
-
3 gates for Software Development
It doesn’t matter whether you use Waterfall or Scrum, or XP, or any other methodology; there are three and only three gates in the process of creating software. The first is the “Idea” gate. At this stage what we’re trying to do is to understand if we should actually build the thing that we’re talking…