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 »