| | |  | Software Engineering | Home » » » Reducing Risk with Software Process Improvement | | | | | | | Product Promotions: | | | | | Description: | | Reducing Risk with Software Process Improvement recommends the critical practices that aid in the successful delivery of software products and services. The author describes the observations that he made over a period of ten years in IT projects and organizations. He focuses on the areas of software development and maintenance, highlighting the most frequently encountered problems that occur due to poor processes. The author derives recommendations from 40 comprehensive assessments of IT organizations.
This book details the potential or real problems each organization experienced, and offers anecdotes on how these problems resulted from deficient practices, what their impacts were, and how improving specific practices benefitted the organizations.
This volume provides valuable advice for project and application managers looking to minimize the number of crises they have to deal with, and for IT practitioners seeking the practical solutions that lead to career advancement. It benefits customers who need to know what to look for before purchasing IT products or services, and helps investors analyze the efficiency of IT companies before making investment decisions. | | | Product Details: | | | Author:
| Louis Poulin | | Hardcover:
| 288 pages | | Publisher:
| Auerbach Publications | | Publication Date:
| May 26, 2005 | | Language:
| English | | ISBN:
| 084933828X | | Product Length:
| 0.89 inches | | Product Width:
| 0.57 inches | | Product Height:
| 0.08 inches | | Product Weight:
| 1.21 pounds | | Package Length:
| 9.4 inches | | Package Width:
| 6.2 inches | | Package Height:
| 0.8 inches | | Package Weight:
| 1.15 pounds | | Average Customer Rating:
|  based on 4 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
 ( 4 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
1 of 1 found the following review helpful:
It's worth the buy!May 16, 2006
By Pedro Madrid
"PM"
I have to say that I'm impressed. It is a very well structured book, similar to the CMMI model structure. It has real life problems and solutions, which you can use to imitate or avoid. Tips and practices that you should and should not do are widely depicted throughout the whole book.
If you are on the try to improve the way software is built in your company this book is a good start that will advice you on what should be done.
It's worth the buy, believe me.
1 of 1 found the following review helpful:
Very practical and entertainingJul 08, 2005
By Kevin, Software Dept. Manager
This book provides very practical information on what counts most in software process improvement. (This is quite useful if you want to get the biggest bang for your process improvement buck.) There's a lot of wisdom packed into this easy-to-read and entertaining book.
1 of 1 found the following review helpful:
Great informationJul 05, 2005
By Joseph
Anecdotes on benefits/consequences of implementing/not improving processes really helped understand why best practices are important, and useful guidance on how to implement them. Easy read that gets to the point. Good explanation of Murphy's Law with details on how to estimate financial losses resulting from risk exposure that can be used in all kinds of situations.
A street-smart approach to improving productivityNov 28, 2005
By A Reader
This book was given to me by a friend who knew I was managing a group involved in improving productivity, and it made me rediscover what improvement meant.
I passed it around to my colleagues to read, so that we could discuss the rationale for implementing specific improvement approaches. Among other things, it made us realize that improving productivity is really all about reducing the number of problems one has to deal with, because fewer problems imply less time wasted in managing crises and more time invested in exploiting valuable opportunities. As trivial as it may sound, this really helped us acquire a new vision of what should be done, and how to go about it.
I now feel better equipped to identify practices that need to be mastered vs. those that are just nice to have. Instead of guessing at approaches that can potentially lead to improvements, my targets are now better defined and my plans more focused.
| | |
|
