Autres vendeurs sur Amazon
+ EUR 2,99 (livraison)
+ EUR 2,99 (livraison)
Managing Technical People: Innovation, Teamwork, and the Software Process (Anglais) Broché – 28 octobre 1996
|Neuf à partir de||Occasion à partir de|
Description du produit
Quatrième de couverture
"Suppose you needed a new computer program. You would want your programmers to give this work high priority and to dedicate their energies to its success. Although no simple procedure can ensure that they do this, there are some methods that usually work....The key is to understand and respect them as professionals and to follow sound management principles. This knowledge and these principles are the subjects of this book."
--from the Preface
This book contains best-selling author Watts Humphrey's practical insights on how to lead technical professionals. In previous books, Humphrey established process as a key factor in successful software development. His advice on how companies and individuals could improve their software process has since been widely adopted. In this new book, he demonstrates the overriding importance of people to the success of any software project. He focuses particularly on the critical role of innovative people, and gives concrete advice on how to identify, motivate, and organize these people into highly productive teams.
Drawing on experience as IBM's senior software-development executive, and expanding on an earlier work, Managing for Innovation, Humphrey presents here proven leadership practices and management techniques that can work in any organization. Given the software industry's dependence on creative human resources, managers will welcome his sound advice on the special challenges encountered in leading technical professionals, and on specific steps managers can take to encourage greater innovation while attaining yet higher levels of efficiency and quality.
Biographie de l'auteur
Known as “the father of software quality,” Watts S. Humphrey is the author of numerous influential books on the software-development process and software process improvement. Humphrey is a fellow of the Software Engineering Institute (SEI) at Carnegie Mellon University, where he founded the Software Process Program and provided the vision and early leadership for the original Capability Maturity Model (CMM). He also is the creator of the Personal Software Process (PSP) and Team Software Process (TSP). Recently, he was awarded the National Medal of Technology―the highest honor given by the president of the United States to America's leading innovators.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
|5 étoiles (0%)|
|4 étoiles (0%)|
|3 étoiles (0%)|
|2 étoiles (0%)|
|1 étoile (0%)|
Commentaires client les plus utiles sur Amazon.com
Most of his advice is not practical, or even possible in the employment situations I've seen (and heard about) over the last ten years or so. I found a few interesting parts, much like I would find it interesting to listen to the tales of any old-timer about the `good old days', and some of his insights about people in general are quite keen.
Some parts really hurt my will to read on. For example, he seems to believe that if a manager can get his team members to work lots of overtime, that higher productivity will automatically follow. Someone who has written books about the use of careful measurements during software development should know better. The evidence I've seen and read (in other books) indicates that regular overtime is a `bad smell' of deeper problems, and a perfect recipe for low quality and ultimately failed projects.
He even claims that the manager's job is to put schedule pressure on the engineers, otherwise they'll take forever and never get anything done. Again, he includes a little anecdotal example. However, with very few exceptions all of the engineers I've worked with hold themselves to certain standards of quality and productivity. Usually management pressure (especially the old time-crunch game) just hurts more than it helps.
Overall, much of his advice doesn't fit with the reality I've been experiencing lately.
I recommend comparing and contrasting Humphrey's advice with that found in "Peopleware" (2nd ed.) by DeMarco & Lister.
Also, for even better book full of `management tips' see "201 Principles of Software Development" by Davis.
Too often technical people are promoted into management with no training. One cannot learn how to manage by merely performing technical tasks. One can learn by reading books like this one.