Customer Reviews

How to Manage a Successful Software Project: Methodologies, Techniques, Tools

5 star:		(2)
4 star:		(5)
3 star:		(1)
2 star:		(1)
1 star:		(0)

 

 

This book covers a good range of basic project management issues. It has good chapters on why projects fail and why projects succeed, with very specific issues outlined. All in all, I found this book to be very practical and hands-on, and one of the best I've seen for getting an overview of the subject. Applicable to more than just software projects; it would also be useful for web project managers and producers. I am hoping an updated version will be coming out, because a large section of the book is dedicated to project management using Microsoft Project 4, now outdated. However, I would still recommend this book for anyone trying to get a good grip on this topic.

This is an all rounded book, from the conceptual to the hands-on practical level. It can ne used as a text book, cook book or "creating ideas" book with appeal to the student, to the neophyte as well as the seasoned project manager.

I found the material well distributed and balanced ; epecially liked the concept of IPDM (iterative project development methodology) and the chapter on outsourcing; the survey results give it more authenticity.

The Microsoft chapters and the templates are also very useful.
I would have liked the templates to be more unified, perhaps tying back with the concepts of phase/activity/task.

Highly recommended as a very good book on project management.

This text is a good resource for educators, students, and IT professionals. So regardless of whether the reader is a novice, academic, or practioner he or she will find it useful. It is well written, and the topics are presented with clarity. The sequence of the topics and overall format of the content is presented in a structured manner and builds on concepts that were discussed previously. This text incorporates teaching and learning techniques that make it appropriate for class room use. The supplementary materials provide readers with opportunities to apply the techniques described in the book.

The introduction of the Iterative Project Development Methodology (IPDM) outlined in this book will update the knowledge and skills of IT professionals whose projects may include n-tier architecture, legacy applications, open systems, Web-based applications, and e-business solutions. In addition to the wide array of methods, tools and approaches presented, I found the discussion on the pitfalls and cost overruns of software projects particularly insightful. Understanding the factors that cause these projects to fail is crucial to assessing the risk factors which are related to specific projects. The authors point out the sources of pitfalls associated with software projects, they explain how such pitfalls can be avoided by the implementation of current project management methodologies. This approach justifies the need for implementing best practices using Microsoft Project 2000.

This book provides comprehensive coverage of software project management, it is an excellent resource.

I am coming back to Microsoft project after many years and found this to be a useful guide to develop a comfort level with this software quickly. The book also describes software management methodology, and describes software managment prcatices that can be applied to development projects especially in a business environment.

The Hands-on tutorial and practioner oriented templates were clearly explained and exercised the most useful and important features of Microsoft's Project.

I recommend this for software project managers, business analysts, or CIO's that have project management experience but have not used software based Project management tools before.

This is a very useful overview of project management process(es). My only complaint is that it doesn't got into enough detail on some of the documents you need to produce. The samples on their website aren't particularly useful, either. One other gripe is that the target audience seems to be employees of companies who run multiple projects, rather than consultant-types like me.

I gave it 4 stars because, in spite of my complaints, this is a very readable book, and serves as an excellent introduction.

Please note that the significant difference is the replacement of the MS Project 4 with a new version. It would have been a more useful reference book if the 2nd edition had included some new topics on managing the internet or e-commerce projects.

I found the book very useful. It contains many lists, examples, and templates that are directly relevant to software project management. It is very focused on the subject. Also found useful chapters that discussed common causes of success and failure, with case studies. Downside is that I found it a difficult book to actually sit down and read. Quite a few chapters were mostly reading outlines and lists. Although the web site was unavailable (11/8), the editor quickly (<24 hours) emailed the templates. Impressive customer service!!

I have read the 1st Edition few years ago. That book is very good for people who are interested in managing software project. I bought the new version in Christmas. It will be most grateful if someone can list out the essential difference between the 1st edition and the new edition, besides the replacement of the Microsoft Project (old version) with the 2000 version so that I can jump directly to the new topic in the book isntead of reading it from A to Z.

A great reference book for all practicing PMs. You can pick up some excellent tips on managing software development projects.