Get it by Tuesday, October 24
, Order by 12:00 PM Eastern and choose Expedited Delivery during checkout.
Same Day delivery in Manhattan. Details
"If you're looking for solid, easy-to-follow advice on estimation, requirements gathering, managing change, and more, you can stop now: this is the book for you."Scott Berkun, Author of The Art of Project Management
What makes software projects succeed? It takes more than a good idea and a team of talented programmers. A project manager needs to know how to guide the team through the entire software project. There are common pitfalls that plague all software projects and rookie mistakes that are made repeatedlysometimes by the same people! Avoiding these pitfalls is not hard, but it is not necessarily intuitive. Luckily, there are tried and true techniques that can help any project manager.
In Applied Software Project Management, Andrew Stellman and Jennifer Greene provide you with tools, techniques, and practices that you can use on your own projects right away. This book supplies you with the information you need to diagnose your team's situation and presents practical advice to help you achieve your goal of building better software.
- Planning a software project
- Helping a team estimate its workload
- Building a schedule
- Gathering software requirements and creating use cases
- Improving programming with refactoring, unit testing, and version control
- Managing an outsourced project
- Testing software
Jennifer Greene and Andrew Stellman have been building software together since 1998. Andrew comes from a programming background and has managed teams of requirements analysts, designers, and developers. Jennifer has a testing background and has managed teams of architects, developers, and testers. She has led multiple large-scale outsourced projects. Between the two of them, they have managed every aspect of software development. They have worked in a wide range of industries, including finance, telecommunications, media, nonprofit, entertainment, natural-language processing, science, and academia. For more information about them and this book, visit stellman-greene.com
|Publisher:||O'Reilly Media, Incorporated|
|Product dimensions:||7.00(w) x 9.19(h) x 0.78(d)|
About the Author
Jennifer Greene and Andrew Stellman have been building software together since 1998. Andrew comes from a programming background, and has managed teams of requirements analysts, designers and developers. Jennifer has a testing background, and has managed teams of architects, developers and testers. She has led multiple large-scale outsourced projects. Between the two of them, they have managed every aspect of software development. They formed Stellman & Greene Consulting in 2003, with a focus on project management, software development, management consulting and software process improvement. They have worked in a wide range of industries, including finance, telecommunications, media, non-profit, entertainment, natural language processing, science and academia. For more information about them and this book, visit http://www.stellman-greene.com.
Jennifer Greene has managed quality assurance teams at multiple software organizations. Her project experience spans many domains, including academic research, financial services and analysis, natural language processing and grants management. She has been responsible for leading process improvement efforts as well as implementing best practices in defect prevention. She is currently leading a major software test outsourcing effort for MicroEdge.
Most Helpful Customer Reviews
Do you work for a software organization who where there are chronic problems producing software on schedule and without defects? If you do, then this book is for you! Authors Andrew Stellman and Jennifer Greene, have done an outstanding job of writing a practical book that describes the specific tools, techniques and practices that a project manager needs to put in place in order to run a software project or fix an ailing one. Stellman and Greene, begin by showing you the vision and scope document. Then, the authors cover the wideband delphi estimation process. They continue by covering project schedules. Next, the authors show you how to do an inspection. Then, the authors discuss use cases. Then, they show you how to do configuration management. The authors continue by showing you how to test plans. They also introduce you to practices, tools, and techniques to your organization's culture. Next, the authors show you why it is important to understand responsibility, authority and accountability. Then, they show you how to prevent the most common sources of failure in outsourced projects. Finally, the authors show you why it's important to understand when process improvement is useful and when it isn't. A project manager can use this most excellent book to diagnose and fix the most serious problems that plague software projects. More importantly, this book contains essential project management tools, techniques and practices, which have been optimized to be as straightforward and easy to implement as possible.
I found this to be an excellent book on software project management. Many of the project management books I have picked up have been either too theory-based or not relevant to the day-to-day problems that exist in software development. I found this book both relevant and practical. This book is divided into two sections. The first section discusses the tools involved in software project management, while the second section discusses how to actually manage a software project effectively. The first section goes through all the tools required to effective manage a software project. The authors dedicate entire chapters to SOW creation, estimation, scheduling, coding (including a discussion on source control providers), and testing. In each chapter, not only do the authors describe the process, but in certain cases, they provide tips to help things go smoother. For example, in the chapter on estimation, the authors provide several different ways to accurately estimate project tasks. I found many of these additional tips very helpful. In the second section of the book, the authors discuss how to effectively manage a software development team using the tools discussed in section one. The authors don¿t specifically use the word ¿agile¿, but I found that most of section two became a discussion on agile practices. Again, the word ¿agile¿ was never used, however, I found it both interesting and refreshing to hear a book on project management discussing how to be adaptable to change. I was very pleased with this book. I thought it was a realistic and well-thought out book on software project management. This book goes a long way toward arming someone with the tools they need to effectively manage a software development project.
I've tried many project management processes and have searched through most of the popular literature over the years trying to find the best way to implement real process change. Much of the literature describes the processes well but ignores the implementation entirely. Applied Software Project Management does a wonderful job both describing the various tools and techniques and giving detailed instructions on how to implement them. The book even goes so far as to describing how to implement processes in an organization that is openly hostile to change and/or process in general. I find this book to be an invaluable resource for any project manager. It's great for newbies, who will learn all the vocabulary and process theory. Experienced project managers will learn new tools and techniques as well as innovatives ways of getting them implemented.