Behind the Scenes at Global-Roam

Fuelled by Stephen’s glowing recommendation of the Thoughtworks presentation “Emergent Design & Evolutionary Architecture”, I went along to Neal Ford’s repeat performance in Sydney this morning.

The talk presented some very sensible sounding ideas on software “design”, and few more on “architecture”. Stephen has covered some points that stood out for him in his post, and here are a couple more that I consider worthy of mention or additional comment.

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 »

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 »

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 »