Try it free |
Read books on your computer or other mobile devices with our FREE Kindle Reading Apps.
|
| ||
| ||||||||||||||||
|
| ||||||||||||||||
Product details
Would you like to give feedback on images?
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Most projects of any substance that I have been involved with seem to fit the 'troubled IT projects' tag defined in the book, and the author presents a clear strategy for avoiding problems before and once they occur. I was particularly interested in the discussion of getting the initial proposal right before proceeding which is where, in my experience, problems often occur and we are then trying to catch up throughout the rest of the project.
I wouldn't say that the book necessarily taught me anything I didn't already know and to a large extent the material covered is really just common sense. However it is really useful and illuminating to see it all encapsulated in the one book.
What's useful is the book offers guidance as to how these problems can be minimised by proper planning and tracking, and responding to changes in a sensible manner. It doesn't try to mandate a particular way of working or running a project (practioners of agile methodologies may find that some of their ways are very compatible) but does present a realistic business case for how projects can be managed well, and be managed badly.
This is an excellent book, not only for your bookshelf, but also for dipping into regularly in order to anticpate problems rather than reacting to them.
|