- Series: Developer Best Practices
- Paperback: 232 pages
- Publisher: Microsoft Press; 1 edition (August 18, 2007)
- Language: English
- ISBN-10: 0735625212
- ISBN-13: 978-0735625211
- Product Dimensions: 7.4 x 0.7 x 9 inches
- Shipping Weight: 1 pounds
- Average Customer Review: 11 customer reviews
Amazon Best Sellers Rank:
#1,034,368 in Books (See Top 100 in Books)
- #329 in Books > Computers & Technology > Networking & Cloud Computing > Data in the Enterprise > Client-Server Systems
- #1150 in Books > Business & Money > Management & Leadership > Project Management > Business
- #2456 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Practical Project Initiation: A Handbook with Tools (Developer Best Practices) Paperback – August 18, 2007
See the Best Books of 2018 So Far
Looking for something great to read? Browse our editors' picks for the best books of the year so far in fiction, nonfiction, mysteries, children's books, and much more.
From the Publisher
Key Book Benefits:
Delivers experience-based guidance about how to get a software development project off to a strong start
Provides metrics and tools to help organize priorities, track progress, and plan assignments
Features numerous useful templates and forms--in the book, and downloadable from the book's companion Web site
About the Author
Karl E. Wiegers is a leading speaker, author, and consultant on requirements engineering, project management, and process improvement. As Principal Consultant with Process Impact, he conducts training seminars for corporate and government clients worldwide. Karl has twice won the Software Development Productivity Award, which honors excellence in productivity-enhancing products and books.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
It is easy to read (In fact, all Wiegers' books are!), this book may be used by both juniors and seniors project managers. Of course, a senior PM will notice details not usually realized by freshers PMs.
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").
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.