The first step is always the hardest

Yesterday marked a very big day in my career. I was able to influence a large, multi-grillion dollar organisation to value software development quality over rapid delivery of rubbish.
It’s only within a segment of the organisation, but it’s probably one of the more influential segments.
It makes me very happy to see the changes that have already gone in place since I joined where the developers are now enthusiastically talking and implementing many good software development techniques, and the quality of the code at the lowest levels is getting better every day.
The next stage was getting the project management and directorship to understand the importance of technical debt, and why it’s good for the project to keep it under control. That breakthrough occurred yesterday, and apart from only having 3-4 hours sleep last night (George was a little excited from his trip to Gran and Bunter) I’m over the moon.
<happy dance>
One small step for Jon, one large step for software quality !!!!
</happy dance>


4 thoughts on “The first step is always the hardest

  1. well done. this is very interesting for me. also working at a multi-gazillion dollar organisation, I too find the same problem. every requirement under the sun and then some, impossible deadline. Project manager signs up to it, halfway through project “on track” yeah right – then sudden descope and architectural compromises…you know the rest.
    I’m interested in what you did that contributed to the shift to their perspective…
    conversations about technical debt around our org lead to blank looks like telling murdoch he can save money by recycling paperclips…seems that with rich organisations the cost of technical debt is not valued, over the perception of speed to market to beat a competitor.
    I’d really like to see a project that deliberately sets out to deliver less than a competitor product, but does it really well, both in terms of quality, and experience.
    ooops starting to rant…

  2. Actually Cam, I had the same blank look when saving money. But as soon as I mentioned shorter time to market they became more interested.
    Took a long time to explain “no, not more people” but after that was all pretty good.

  3. re: explaining “no, not more people” – that’s the real trick isn’t it?
    except, I’m saying at the moment “Oh no! Not *more* people!” Big project bandwagon syndrome.

Comments are closed.