Customer Reviews

Practical Project Initiation: A Handbook with Tools (Best Practices (Microsoft))

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

 

 

There is one word that particularly comes to mind when I think of Karl Wiegers: solid. I've been reading Mr. Wiegers articles and books about software for at least a decade, and Practical Project Initiation is as solid as I've come to expect. I use the word "solid" specifically to describe the kind of advice that Wiegers offers, which is typically based on real world experience and research, never on conjecture, received tradition, or trends. Karl is all about doing software right and helping you do the same.

There are several things I like about this book. First and foremost, I like that it is short and narrowly focused on the topic of starting new software projects--a neglected area to be sure. Much like Robert Galen's recent book Software Endgames focuses on getting a troubled project over the finish line, Practical Project Initiation focuses on the start of the process, with the idea of helping you keep your project from getting into trouble in the first place.

At 200 pages, the book is short (by software book standards anyway) not only because the focus is narrow but also because Wiegers is concise; there is almost no fluff here. I think Wiegers knows that when you need a book like this, you need immediate help getting your project off on the right foot, not three months worth of study material. I was able to read it all the way through pretty quickly, and much of the material is designed so that you can come back to it later for reference purposes.

The ironic part of what I've said about the book's narrow focus is that the first 25 pages of the book may actually be one of the best short introductions out there to the broad topic of project management.

Another thing I really like about Practical Project Initiation is that Wiegers does not steer you in the direction of a particular process, or try to propose Yet Another Great Methodology, or try to convince you of the One Right Way to develop software. (In fact, I seem to remember an essay by Wiegers from a few years ago called "No New Models!") Weigers makes room for whatever methodology/process you are using, and if you're really not sure what methodology you are using or should be using, don't worry--just follow the foundation advice in this book, and you'll be okay. Another way of saying this is that, while the book overall does have a strategic scope, the focus of the material is very tactical. The tactics Wiegers suggests can be used on the most agile Agile project or the most formal "heavyweight" project.

Before this review gets too long, I want to highlight the wealth of "tools" that come with this book. Many of these are tools in the literal sense, in the form of worksheets, checklists, and templates that are printed in the book and that can be downloaded for free. But the whole book is full of tools in the figurative sense also--things like the wideband delphi method for estimation, a feature triage process for figuring out what to include in the project when there's just too much scope, and techniques for identifying and managing risks.

If you, like me, just like to geek out on software books and pick up new techniques and insights, I recommend this book for reading and loaning out. If you are more squarely in the target audience of the book--being a person who is tasked with getting a software project off the ground--this book is a must-have. Get it fast, read it fast, and put Wiegers practical advice into action right away.

This book, while good didn't thrill me. It covers some software projects management fundamentals and best practices. It's short, simple and and easy to read, addressing a broad range of topics such as project preparation, project charting, risk management, principled negotiation, project metrics, project retrospectives. In my opinion it's too high-level and most of the topics are already well covered in other books, such as "Rapid Development" by Steve McConnell or "Competitive Engineering" by Tom Gilb (both excellent and quoted in this book). The landmark book by Karl Wiegers is still "Software Requirements".

Approximately 200 concise pages of very good advice. Several useful tools. Another very good book from Karl.

As with any book I have read by Karl Wiegers, this one was clearly written, and included a lot of practical advice. I can easily recommend it for anyone interested in improving project outcomes, which is really what the initiation phase of any project is really about.

In addition to project initiation, this book includes helpful advice on tool adoption, estimation and measurement practices, and project retrospectives (analyzing projects for "lessons learned").

A key to running successful is getting them set up well--anticipating likely problems (not just risks, but also mid-stream changes, for which you'd want a change-control process). I also like that this book not only has solid advice, but also has good sample templates that you can use for many project-related documents.

Project inception is the most difficult step for every project. If not done properly, the whole project is going to fail.

In my opinion chapter 3 is the most useful. It concentrates not on how a project should be started, but rather on whether it should be undertaken.
More often than not a project is doomed to fail and should not have been started in the first place. Therefore it is very important to concentrate on the right projects, which are those which are aligned with the business objectives of the enterprise.

Chapter 11 describes a process called "wideband delphi" which is used to gain useful estimations. Wideand delphi allows a group of people to find more accurate estimates.

After all a recommended reading for every manager and project manager.

This book is a very good quick reference and overview for looking at the tasks for particular parts of requirements gathering with customers. I've used this as a reference often to organize my todo lists before visiting with clients as well as assessing what I've missed or could have done better after a site visit.

Writer is awesome and right on. Book received in great shape and quickly. Recommend the seller.