am 19. September 1999
Firstly, don't let the title put you off -this book is relevant to a lot of people who wouldn't call themselves "sofware engineers" or "managers" - it's also highly relevant to systems analysts / designers & just about any sort of IT consultant, amongst others.
What separates this from most other books on software development is that just about every page is obviously written by someone who has been there and done it (recently), not just talked about it. The main ideas of the book (evolutionary delivery, defining ojectives as either "functional" or "attributes" ) may not seem revolutionary, but apply it and it could revolutionise your project and maybe career. No IT book I've ever has ever affected my own work so profoundly.
It's also well written and exceptionally well laid out. More please, Tom!
am 29. September 1999
I found this book hard to read. I often had to force myself to read further, although the ideas and principles described are important and should be required knowledge of any software engineer and SE manager (which does not mean that they necessarily apply to all projects).
The book contains endless redundancy and lots of hard to understand details of projects the author has worked on. One chapter even contains excerpts from other books and articles that confirm the author's views - as though the author feared he hadn't been convincing enough (that wasn't the problem).
In summary, the book should have had half the length and that would have still covered the same content. It might be interesting to readers new to the principles of evolutionary delivery, measurable attribte objectives, and inspection.
am 18. Februar 1997
Gilb introduces three ideas that may not be new, but
extremely useful for software projects. Evolutionary
delivery, or delivering small parts all the time, while
getting feedback; formal inspections, which will save
time and hassle; attribute specifications, to help you
set a clear goal. I guarantee that this book will see
software in a fresh, new perspective!
am 26. Juni 1998
Gilb covers only a small portion of "Software Engineering Management" in detail. Other important issues are either not addressed at all or receive only cursory treatment. Still, what it does go into depth about it usually well thought out and makes imminent sense. I'd say it's worth reading, but it may be a bit expensive for it's narrowness.
am 19. Mai 1998
This book covers three main topics: evolutionary development, requirements management, and inspections. A good introduction to all three, but if you plan on trying evolutionary development, I also suggest reading the pertinent sections of Rapid Development by Steve McConnell.