Rating: 
Summary: Good Book on Software Project Management
Review: This is a book that lives up to its title. It begins by explaining the pitfalls of the traditional models, and then introduces the reader to the new "Architecture First, Iterative" model. The material is organized well. Each chapter has something good to offer. Some chapters explain a concept in great detail, and just when you get a feeling that you are lost, there appears a section that makes "pragmatic" sense!! Good explanation about development Life Cycles, Workflows and the Iterative development model. There is a lot of emphasis on early integration, which I believe is the right way to develop software. Royce points out that Software Testing (Assessment) should not be treated as a separate entity in the software development life cycle. Instead it should be woven right into the framework, thus becoming an integral part of each phase in the Life Cycle - again, a very crucial and significant idea. One may have to tweak the ideas to suit specific needs, but the book delivers the right message in general. A must read for Software Project Leads and the likes......
Rating: 
Summary: Unified Framework means using modern process such as the UP
Review: This is a modern book on Software Project Management with a recent copyright unlike the others in the bookstores that date back some years.The subtitle "A Unified Framework" indicates that this book is about Project Management using a modern Software Development Process such as the Unified Process and touts the advantages of using a standard modeling language such as the Unified Modeling Language. This book offers valuable top 10 lists of best practices for modern project management. The conventional and modern aspects of software project management are compared and contrasted in the first part of he book. The later part of the book focuses primarily on modern aspects. This is a great book to read if you've first read the Unified Modeling Language User's Guide and then the Unified Software Development Process. This book fills in the missing project management piece from the other two books.
Rating:
Summary: Unified Framework means using modern process such as the UP
Review: This is a modern book on Software Project Management with a recent copyright unlike the others in the bookstores that date back some years. The subtitle "A Unified Framework" indicates that this book is about Project Management using a modern Software Development Process such as the Unified Process and touts the advantages of using a standard modeling language such as the Unified Modeling Language. This book offers valuable top 10 lists of best practices for modern project management. The conventional and modern aspects of software project management are compared and contrasted in the first part of he book. The later part of the book focuses primarily on modern aspects. This is a great book to read if you've first read the Unified Modeling Language User's Guide and then the Unified Software Development Process. This book fills in the missing project management piece from the other two books.
Rating:
Summary: A must have.
Review: This is one of the top books on software project management. One of the best on the suject.
Rating:
Summary: Best software project management book ever
Review: This was the most balanced, sensible software project management book I've ever read. We are in the process of implementing Rational Objectory, and this book captures and presents the methodology's essense in a clear, well-architected out fashion. It was as if the author followed the practice outlined in his book in writing the book itself. This will be must reading for my project managers. I've read over 70 books on OOA/OOD, software project management, etc., and this is the only book that succeeds in utilizing a rational, comprehensive, 'real-world' philosophy to systematically and successfully design, develop and deploy software. A truly 'shrink-wrapped' book that's useful and effective straight off the shelf!
Rating:
Summary: Updated and Forward-looking View of SW Project Management
Review: Walker's book is somewhat irreverent, but wholly pragmatic. He is not afraid to gore some of the sacred cows of software project management in search of updated principles. He notes that many of the tried and true principles were first generalized in the 1960s and 1970s. As our tools and understanding of the software development process have matured, these prinicples need to be revised - indeed, some need to be discarded. The result is a book that is pithy and frank. Walker makes no apologies for his views and he shouldn't. They are based on his personal experiences and in my view more accurately reflect what successful software project managers do today. He explains the rationale for his statements and uses tables and figures to capture them in an easy to read form. This is a MUST read for anyone developing software in today's tool rich environment and with today's understanding of the things that make software projects successful. It should also be used as the required textbook for software project management courses in every university that offers a software engineering curriculum.
Rating: 
Summary: Business case for an iterative process
Review: Well-researched, well-thought, and well-written book provides a compelling business case for an iterative software development process. Rather than focus on the mechanics of the Unified Process, as one might expect, the author presents justification for transitioning from a traditional software engineering approach to an iterative approach. Conventional software engineering is first presented, along with its drawbacks. The changing software landscape is examined, and future success factors are identified. The factors are then tied into the new process. Thorough coverage of many different angles, including an excellent section on metrics, estimation models (and the evolution of COCOMO), team development, culture changes, etc. Great read.
Rating: 
Summary: Good in theory, bad in practice
Review: When I read the reviews of this book, I got interested and purchased the book. The book was a disappointment. It may be a good academic book and relate to the CMM, but it does not provide any guidelines as to how to deal with the details of what you encounter in projects in real life. I wonder if these techniques have really been applied in real life. There is much discussion of methods, but little on what it takes to use the methods. The book does not handle the many issues that arise when you try to manage a lot of work, with few staff, and not enough time. Very disappointing.
| 
