Behind the Scenes at Global-Roam

(Excuse the sad pun)

This week we went out for lunch with one of the guys in the office who was celebrating his birthday.  One of the small things we do in the company to celebrate the uniqueness of every individual (that’s a tick – thanks for suggesting it those years ago, Ricky).

Anyhow, as we were waiting for our meals to arrive in the local steakhouse and conversation drifted to some of the more detailed technical nature of software development, my mind began to wander (yeah, that’s a cross) and I pulled out the latest copy of INC, which had just arrived in the mail and started to browse (yeah, another cross)!

An article in the magazine caught my attention, as it provided a few pointers about the workplace culture that we are working to cultivate internally.

Given that I have been asked a couple of times this week by candidates for our Chief Software Engineer position about our culture (how it is now, and how we want to evolve it, over time), I thought it would be useful posting this (though I know it does not absolve me of the crosses above). 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 »