Отличная книга. Написана в форме художественной, а не деловой форме, легкое изложение, но при этом в конце каждой главы – важные тезисы.

Я и сам – разработчик с многолетним опытом, но, несмотря на этот опыт, всё равно нашёл для себя несколько очень важных моментов, касающихся этапа проектирования, «ценности» свехурочной работы, отношений в коллективе.

Рекомендую прочесть книгу не только project manager'ам, но и всем, кто занимается разработкой программного обеспечения. ( )

Interesting option : try to make a project management book as a novel. I am not convinced by the business points, probably obvious enough but the book is really funny to read. ( )

In this book you follow along as a fictional project manager copes with a slew of issues, discoveries and revelations in the midst of his impossible project.
For me the genius in this book lies in the protagonist keeping a journal of lessons learned from each day on the project. On my first day at work since completing the book, I unconsciously wrote myself a note in the same exact style employed in the book ("Build one phone, not six applications").

Here's a taste of some of my faves form the book - but you really must read for yourself because much of the learning takes place within the book's narrative.

* No matter how serious the threat, the work still won't get done on time if the time originally allocated for it was not sufficient.
* Think of a jelled team - ready and willing to take on a new effort - as one of the project deliverables
* The danger of standard processes is that people will miss chances to take important shortcuts
* There is no way to get projects to perform substantially beyond the norm without making large reductions in the total amount of debugging time
* Keep meetings small by making it safe for unessential people not to attend.
* Awful suspicion: Projects that set out to achieve "aggressive" schedules probably take longer to complete than they would have if started with more reasonable schedules. ( )

Recommended to me by Mohan Kartha, who writes: The book is "The Deadline" by Tom DeMarco - one of the gurus of software methodology. I consider this book a must read for anyone in the software or technology development or marketing industry. It is a great overview of the issues involved in project managment or small and large teams. There is considerable discussion of how to measure the success of a project team rather than just trying to manage "by feel".