Behind the Scenes at Global-Roam

You don’t have to of read much of this blog to realise that over the last few months Global-Roam’s software development practises have been changing as we adopt a more structured, and more agile, approach.

As has been made clear by a recent visit by Steve Hayes from Cogent, and our other attempts to learn more about agile, there is a thousand ways we can improve. This makes it easy to be stunned, like an animal caught in headlights, and instead do nothing.

So last week, Stephen and I worked out what the next level of low hanging fruit was, and have put together this plan to reach it.

read more »

This morning I was the most casually dressed person at a Thoughtworks run seminar called “Emergent Design and Evolutionary Architecture”. The seminar itself was extremely well planned and executed, despite the lack of effective air conditioning. The speaker was an American named Neal Ford, who Thoughtworks had flown out to Australia to speak at these events (there are two more, which you can catch for free in Sydney and Melbourne).”
read more »

I was speaking with someone today, who stated that they had inferred I would have a tattoo on my butt reading “Agile Rocks” (or something like that).

I do apologise for any misconception caused by posts such as this one.

I also apologise for the images inadvertently conjured up by the first sentence.

read more »

After posting my review of Kent Beck’s webinar back in November, I contacted Kent to confirm it was ok with him to publish.

As part of doing this,  I asked Kent if there were good people in Australia who could provide us assistance in transitioning to Agile.

Hence, Kent pointed us at Steve Hayes of Cogent Consulting, who we have been recently using to provide us some greater understanding of different aspects of Agile (though I read recently that Steve is planning to leave)!

In long-hand, you will be known as our:

General Manager for Discerning, Developing and Delivering what the Customer Wants

That’s a bit of a mouthful, so we have shortened it to a variety of titles used on this blog and elsewhere:
1)  GM Software
2)  Chief Software Engineer
3)  Director of the Product Development “Factory”

I would stress that all three aspects of the role are important.

read more »

A central part of the changes we’re making internally, stemming from the Autopsy 2 process, is that we’re aiming to get very clear about “why?”

Why does our company exist in the first place?

Why should our customers care about what we’re striving to be?

Why would anyone be led by me?

Shirlaws call these questions “context”. read more »

Perhaps a year ago, we bought our first copy of this book. One of the guys read it then, and highly recommended that we get a number of copies such that everyone in the office could read (alas no book review online then).

We did this, and a number of others did read the book – giving similarly rave reviews.  Coincidentally, they commenced a software development project (our “UPIP project”) with the “lessons learnt” still fresh in their mind.

However, the wheels fell off – leading to the UPIP project being canned indefinitely.  This was one of the major triggers for me to instigate our Autopsy 1 process, which continued into the Autopsy 2 process, my stipulation that we were going to go Agile, and the commencement of our process for looking for our Chief Software Engineer.

Note that there is plenty more we can learn from the many things that went wrong in the UPIP project – with a view to improving ourselves for the future.  When I find the time, I will post a more detailed retrospective as a restricted post, just about that project.

Don’t get me wrong – I understand that we had significant shortcomings that were the root cause of our calamity.  For instance, it became clear through this process that our team collectively had no major project management experience – hence a read of a single book (no matter how good) was not going to make them competent (especially with respect to a complex project).

However I did wonder how a project to could go significantly off the rails (and in the early stages) so soon after a number of people had read, and raved about, this book. read more »