Desarrollo Y Gestion De Proyectos Informaticos Steve Mcconnell Pdf

Mar 23, 2018  Descargar Desarrollo y Gestion de Proyectos Informativos.

I can hear some of you exclaiming, 'How can you possibly recommend a book about software scheduling published by Microsoft Press and written by a consultant to Microsoft?!' Well, put aside any preconceived biases. This is a tremendous book on effective scheduling software development, and it drinks deeply from the wisdom of all the classics in the field such as Brook's Myt I can hear some of you exclaiming, 'How can you possibly recommend a book about software scheduling published by Microsoft Press and written by a consultant to Microsoft?!' Well, put aside any preconceived biases. This is a tremendous book on effective scheduling software development, and it drinks deeply from the wisdom of all the classics in the field such as Brook's Mythical Man Month -- and is likely well-informed by McConnell's experiences, good and bad, in Redmond. The nine page section entitled 'Classic Mistakes Enumerated' is alone worth the price of admission and should be required reading for all developers, leads, and managers.

Here are some types of the 36 classic mistakes that McConnell describes in detail: People Related Mistakes Heroics Adding people to a late project Politics placed over substance (etc.) Process Related Mistakes Abandonment of planning under pressure Planning to catch up later 'Code-like-hell' programming (etc.) Technology Related Mistakes Silver-Bullet syndrome Overestimating savings from new tools or methods Switching tools in the middle of a project (etc.) I suspect that if you've ever been involved in software development, you winced after reading each of these nine points. And you will learn a great deal from the remaining 640 pages about concrete solutions. My only substantive gripe: cheesy Powerpoint graphics. Nonetheless, this book is Very Highly Recommended. How can I add any value to the multitude of reviews that obviously say 'You must buy this'? When I was working 80 hours a week - this was the only book I read cover-to-cover. When I lent my book to one of my staff and he left the firm, I bought another copy off the shelf within 24 hours (I couldn't wait for Amazon's delivery time).

This was after having read the book twice. This is the only book I have bought 3 copies: one for work, one for home, and one to share. It's the only book which caused me How can I add any value to the multitude of reviews that obviously say 'You must buy this'? When I was working 80 hours a week - this was the only book I read cover-to-cover. When I lent my book to one of my staff and he left the firm, I bought another copy off the shelf within 24 hours (I couldn't wait for Amazon's delivery time).

This was after having read the book twice. This is the only book I have bought 3 copies: one for work, one for home, and one to share. It's the only book which caused me to specifically make a trip to the bookstore to get a signature and hear a writer speak. This is the 2nd of McConnell's books I've read. Code Complete was great.

I couldn't believe anything could be better but this book is it. It repeated a few facts and figures but it's worthwhile to have it reorganized and re-presented for a different view.

This book has led me to be a confirmed McConnell reader. His other books are good, but this is his best. Unfortunately, my expectation is so high now that his subsequent books are not impressing me as much. Because of this book, I will attend my second course from his company - even if it means flying into Seattle's rain.

One book and he's hooked me for literally a thousand dollars - that's an effective writer! I think this book is really showing it's age. McConnell's advice feels genuine, but the data is based on experiences from the early 90s.

A lot has happened in the software world between then and now so there are many things that don't fit with some of the best practices that modern development embraces. Unless you're staying on top of how companies do development today, it's hard to filter out what is outdated advice versus what is still relevant.

Therefore, in spite of the book having some good I think this book is really showing it's age. McConnell's advice feels genuine, but the data is based on experiences from the early 90s. A lot has happened in the software world between then and now so there are many things that don't fit with some of the best practices that modern development embraces. Unless you're staying on top of how companies do development today, it's hard to filter out what is outdated advice versus what is still relevant. Therefore, in spite of the book having some good information, I can't recommend it strongly because uninformed readers might be lead astray by practices that have proven themselves to be fads (I'm looking at you, JAD) or are just mediocre advice.