Latest posts
-
Scrum: It’s supposed to be simple
How difficult have we made it? If you go to the agile manifesto website, the manifesto itself is articulated in clear and succinct terms. Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan Just below this there’s another paragraph, which is often overlooked. That is, while there is…
-
Bring a little chaos
Chaos Engineering leads to higher resilience Chaos Engineering sounds counter intuitive, it sounds completely opposite to getting the most reliable software deployment possible out there and into Production. But it works, and it works because it forces people to think differently. What is Chaos Engineering? The Principles of Chaos Engineering website defines it as “the discipline of experimenting on a…
-
Failure is not an option
Why do Digital Transformations fail? Why is it that transformations fail? Why is the blame often laid at the door of IT? It’s not (always) your fault Let’s not pretend failure isn’t ever IT’s fault, often we have an important part to play in either the success or failure of a project. However, as the agent…
-
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…