Agile Software Development

The downside is that a cover-to-cover reading will feel a bit belabored; the point couldve been made in a bit less space. Especially noticiable were the places where sections had been copy/pasted from earlier sections of the book. I can see where it adds to random-search readability, but the third time I read the same anecdote, I was feeling a bit abused.

Also, there was a very interesting framework around levels of criticality that I was really interested in. However, he had one category that implied loss-of-life. Okay, I got that. Then, later in the book, he talks about categorizing a financial project (that nowhere involved mafia hitmen) as that level! I guess I understood the analysis process, but the labeling of the levels totally lead me down the wrong path. I was thinking space shuttle, and he went RC racer. Not necessarily a bad thing, but I left the book not too confident that I was as grounded in the categorization process as I couldve been.

The "successful" word is very important - I have read many books on software development that provide helpful techniques and methodologies, but dont really have much bearing on the success of your project. I have seen specific techniques and methodologies applied extremely successfully in some teams on some projects, and really poorly for others. Personally, I am interested in being very successful in every project I embark on, and Cockburns book is the only one I have ever read that contains everything you need to know to be successful every time. It is the essence of software development.

Over the years Ive developed a good feel for how a great project runs, but have found it remarkably hard to communicate what it is that makes the difference between successful and failed projects. I was delighted to find that Alistair Cockburn has worked out how to articulate the difference and how to make sure that your projects are the successful ones.

For anyone that has done the hard yards through real-world software development projects where time-to-market is a crucial factor, you will be overjoyed when reading this book. You will find you now have a vocabulary to use when talking to others about your projects. After every chapter you will find yourself bursting with excitement to tell someone about what you have learned. The book will change the way you look at your projects and will give you the key to being successful.

For novices to software development, read this book and count yourself lucky that you found it right at the start of your career. The amount you will gain from Cockburns insight is immeasurable.