- Hardcover: 408 pages
- Publisher: J. Ross Publishing (July 1, 2010)
- Language: English
- ISBN-10: 1604270349
- ISBN-13: 978-1604270341
- Product Dimensions: 6 x 1.1 x 9 inches
- Shipping Weight: 1.4 pounds (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #2,059,333 in Books (See Top 100 in Books)
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.
Mastering Software Project Management: Best Practices, Tools and Techniques
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
Customers who viewed this item also viewed
Customers who bought this item also bought
Mastering Software Project Management is a masterpiece of clarity, organization and depth of practical knowledge. Read it thoughtfully and with care as it is a rich treasure trove of experience and insight. Remember the old saying--do not work hard, work smart--this book will give you the knowledge and tools to do just that. --Robert C. Anderson, Director, Process Development and Quality Assurance, Computer Aid, Inc.
This book provides you with tools, techniques, and practices that you can use immediately on your own projects. It supplies the information you need to diagnose your team s situation and presents practical advice to help you build better software... a must read! --John Zielinski, Project Manager, IBM Global Services
From the Author
Written from the standpoint of a project manager in a software development organization, this unique guide explains software project management in its entirety, including project acquisition, and execution with backward linkages to concepts that play a facilitation role in successful project management and delivery. It provides all the guidance, best practices, tools and techniques needed to master software project management and achieve superior results
Try the Kindle edition and experience these great reading features:
Showing 1-3 of 8 reviews
There was a problem filtering reviews right now. Please try again later.
Most of the authors I have read are either too biased towards their one preferred project management approach, or they present project management guidelines as cold, clinical reference materials.
That is why it was a genuine pleasure to read Mastering Software Project Management: Best Practices, Tools and Techniques. This book provides the level of detailed information that you would expect from a comprehensive project management guide, but with a refreshingly human touch that most other books lack. Equally important, Mastering
Software Project Management provides an extensive range of clear and unbiased information that lets the reader decide which approaches and techniques are the most appropriate for each project. It is, by far, the most usable A to Z guide of IT project management that I have ever read.
If you are at the beginning of your IT project management career, this book provides you with a comprehensive overview of everything you need to know, from how to secure the initial budget acquisition for the project to conducting the post implementation review. And, more importantly, why you need to know it.
If you are an experienced IT project manager, this book expands on your existing knowledge, providing you with alternative approaches to achieving successful outcomes as well as useful templates for structuring your work.
I have found this book to be an exceptionally useful resource and I would strongly recommend it.
Project management is such a large topic that a single book cannot really claim to cover it all. This book introduces a large number of topics but does not cover a lot of detail. The book is more intended for people who are new to project management. This book would be a valuable text to use in conjunction with a training program for new project managers. It seems worthwhile to use the book to frame discussions and try example templates.
I liked, for example, the material on configuration management (CM). As a developer it sometimes feels like CM represents extra work that doesn't really help get the job done. As a project manager, you learn that CM is absolutely necessary. Here there are specific suggestions about configuration planning and reporting with sample tables for collecting CM data. There are also suggestions about how the PM can use the data. While the PM may not do this work himself, he must know that it is performed and the data CM provides is a very useful indicator of progress and problem with the product.
The first few chapters cover very useful background, which PM's-to-be in particular, would find helpful. These discuss the various types of development approaches, different PM approaches to the SDLC, etc. For PM veterans, these chapters recollect that software development is continuously evolving, and new and adapted techniques are at the PM's disposal. A reminder that PM's should never be content with doing projects one way, but need to continually reach out and drive change and improvement.
The meat of the book is contained in its detailed, almost cookbook-like chapters that take the reader from project inception all the way to successful delivery. The really nice part is that if you're a project manager in the midst of a project, you can jump to any one or more of the chapters that pertain to the phase of your project and find useful guidance, advice, best practices, templates, etc. So a cover to cover read is not a necessity from the get-go and benefits from the book can be realized immediately. It's not often you find this instantaneous value in a book. The pragmatism in the way it is organized is refreshing. And because of this, it's the type of book you can keep on your shelf and reference over and over.
When I picked up Mastering Software Project Management, I was very glad to see a chapter devoted to Agile. Having used this methodology successfully on a few projects, it's very important that PM's familiarize themselves with how to successfully drive and manage Agile projects.
And of course, sometimes (some would argue often!), projects go awry and PM's are ineffectual. Mastering Software Project Management dedicates a chapter on project pitfalls. These are the landmines that PM's need to steer clear of if they want to have any hope of achieving projects goals. This chapter includes excellent summaries of where I have personally witnessed the cause of projects going off the rails. In some cases, these were unfortunate reminders that I hope to never revisit!
The book contains a substantial "Appendix" section. These 10 or so appendices could have just as easily been included in the body of the book. To me, an appendix is 'optional' reading or an appendage to a book. This was not the case with appendix in Mastering Software Project Management. The appendices are as substantial in content as the rest of the book. The chapters I enjoyed the most included productivity (we all want our projects to be more productive), issue resolution (a very important concept that needs to be mastered, the absence of which causes projects to miss targets or even fail) and managing people (a challenge on most projects given the diversity of projects' people composition). In the section 'Managing Difficult People' in the 'People Management' chapter, I particularly enjoyed associating the different types of people with those I have encountered over the years. :)
I have nothing but accolades for this book. It's pragmatic, easy to read, useful (the templates alone are worth the cost of the book) and organized to facilitate easy reference. If PM's mastered the approaches and advice provided, they would achieve an invaluable position as an integral part of the software project lifecycle and associated processes. At the end of the day, we want our projects to be on time, on (or under) budget and our customers (whether they are internal or external) to be happy, and hopefully return with more business! The authors clearly understand this mission. Hats off to them for writing this exceptional book.
P.S. If you read this review, sorry it was so long. I'm a great believer in books that can help improve the effectiveness of software development, and this was one of them, so I got a bit carried away.