Your Memberships & Subscriptions
Follow the Author
Getting Results from Software Development Teams (Developer Best Practices) 1st Edition, Kindle Edition
Learn best practices for software development project management—and lead your teams and projects to success. Dr. Lawrence Peters is an industry-recognized expert with decades of experience conducting research and leading real-world software projects. Beyond getting the best developers, equipment, budget, and timeline possible—Peters concludes that no factor is more critical to project success than the manager’s role. Drawing on proven practices from allied industries such as business, psychology, accounting, and law, he describes a broader project-management methodology—with principles that software managers can readily adapt to help increase their own effectiveness and the productivity of their teams. Unlike other books on the topic, this book focuses squarely on the manager—and shows how to get results without adopting philosophies from Genghis Khan or Machiavelli. (There is mention of Godzilla, however.) Packed with real-world examples and pragmatic advice, this book shows any software development manager—new or experienced—how to lead teams in delivering the right results for their business.
From the Publisher
- Delivers methodologies and metrics for developing and analyzing project plans that work - Provides principles based on extensive managerial experience, with many real-world examples - Focuses on the management role, in contrast to many books in the field that cover multiple roles on a team--This text refers to an out of print or unavailable edition of this title.
About the Author
- ASIN : B00JDMPP56
- Publisher : Microsoft Press; 1st edition (April 30, 2008)
- Publication date : April 30, 2008
- Language : English
- File size : 4120 KB
- Simultaneous device usage : Up to 5 simultaneous devices, per publisher limits
- Text-to-Speech : Enabled
- Enhanced typesetting : Enabled
- X-Ray : Not Enabled
- Word Wise : Not Enabled
- Print length : 450 pages
- Lending : Not Enabled
- Best Sellers Rank: #1,175,129 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
About the author
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The Author does this in a mere 276 pages. Considering that there are volumes written on any one of the above topics, that is very amazing. The writing is very clear and well laid out. Even if you have read some of the volumes within these areas, this book is very nice, focused read of overall management of a software project.
There are areas in which I would have liked to have read more details and areas that I would liked to have read less ( this is why I gave a rating of 4 stars instead of 5 ). But, I am sure that those areas would not be the same as what you would like. It is very difficult to cover this thoroughly for everyone. Lawrence Peters did an excellent job, overall.
I would highly recommend this book, even if you have read books on the stand-alone topics. Having everything in one, focused read is very thought provoking.
Also, I would recommend this to all IT technical managers. I have seen so many fail at their endeavors and not even realize it. This book will help you to become more successful in your jobs.
There is fairly deep treatment of a variety of planning styles, project lifecycle models, and even information about how to best motivate your team. I particularly enjoyed the ties between what motivates people (like early involvement with planning and release date specification) and how that is an aspect of a variety of different planning frameworks. He also does a great job of providing specific examples of how to let the team, company, and situation help define the right process, rather than always doing exactly the same thing.
The only thing I didn't enjoy as much was the treatment of some of the more in-depth planning models. It felt like there was a lot of detail, but I still didn't come away with a good idea of where to get started with them if I wanted to use them immediately. A summary section at the end of each presentation with pointers to good "how to do it" books and tools (as opposed to the existing references to the definitions of them) would help. Also, some of the relative terms like small, medium, and large projects that he used to help with decision-making could use some clarification. After years of working at Microsoft, I still consider anything under a quarter million lines of code small, and it takes about 20 million to make a large project. I don't know how those numbers relate to his breakdowns.
Reading this from cover to cover has introduced me to parts of our team that are just flat-out missing. Without this book we would have continued to focus on fixing the parts of our team that exist instead of adding in the parts that we didn't even know were missing.
Although I don't see us being able to 'do everything' in this book, it has been incredibly helpful to see all the parts of a team put together in one book.
This book is kind'a old but every bit of it seems relevant today.
This is a very serious book - essential reading for software project managers. Dispels the myth (or sometimes a personal self-delusion) that project managers just happen to be born with natural skills.
Although software project centric, it is broad enough to be of interest to anyone involved with technology projects at any level. It is recommended for upper management who might be interested in installing a "culture" of consistent project management disciplines (and successes). It might also be useful for HR personnel in screening candidates. Development team members will also benefit.