Nothing Substantial
Rating:
2 / 5
This book is beneficial only to those readers who have never managed a software development project. The author essentially provides a high-level overview of the project management processes used at Infosys, an organization which reached CMM level 5. The book lacks any real substance and I walked away from it feeling I hadn't learned anything new.
One would be better served picking up a copy of PMI's PMBOK to learn about coherent project management processes.
Worth reading and heeding
Rating:
5 / 5
This book is important for three reasons - (1) it lays out a mature, viable project management approach, (2) the approach is proven in practice (hence the title) in a large organization, and (3) it shows that by-the-numbers approaches to complex endeavors is not necessarily theory. An added bonus, if you are in an organization that is using CMM key process areas or are working on a CMM initiative, this book aligns to that as well.What I like is the way this book lays out the how's of project management in a complete, detailed manner, and how it takes those how's from theory to practical application by providing real cases and the author's own insights and experience. Unlike other books, no matter how well written, this one will give you the confidence that the approach can be done. All of the critical success factors of a well managed project and the techniques for attaining them are there - excellent planning and estimating, scheduling, execution and control practices are provided. More importantly, this book shows how quality is interwoven into the approach, as well as key metrics and how to gather, manage and use them. Since this information is provided within the context of cases and real examples, readers who are serious about managing software projects will be struck by the realism and how to apply mature processes and practices during the project. I also like the insights into InfoSys, which is one of the most highly respected consulting and integration firms in the world. Reading this book solely for competitive intelligence purposes is a valid reason. However, reading it to become a top software project manager who can deliver on time and schedule is an even better reason to read this book. It is one of the best written books on a discipline that is both difficult and has a spotty record when it comes to success. Following the practices in it will assure success.
A plan for success in software development
Rating:
4 / 5
In all things, we learn best from those that are the best. Infosys, a software development firm, has one of the best track records in the successful completion of software development projects. Their level of success is most impressive in an area where somewhere close to one-third of the projects either are canceled or experience cost overruns in excess of 125%. They attribute this level of achievement to a sound and repeatable management strategy and the purpose of this book is to articulate that strategy.
This is software development that is organized, from the first sketch of an idea to the last comment in the project post-mortem. The key points are to plan, but be flexible in the implementation and never, ever miss a chance to learn and record something new for the next project. It is also important to track the progress, based on estimates that are reasonable and not motivated by any personal or political agenda. Every listed feature is to be given a priority based on the value to the end user, rather than what the management or developers think is a cool thing to do. This may seem like an obvious point to make, but in fact features often get pushed up the priority scale because someone in the development chain demands it.
General Dwight Eisenhower once said something like, "While no plan survives first contact with the enemy, I still cannot fail to plan." The reason behind this is obvious, in that people who plan ahead are always better at adapting to new circumstances than those who have no plan before they start. That is the primary point in this book, and it is one that you should follow, as planning for each step in the development cycle is examined in detail.
|