
Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$27.50$27.50
Ships from: Amazon Sold by: MbBooks
Save with Used - Very Good
$12.37$12.37
Ships from: Amazon Sold by: The Green Choice Store

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the authors
OK
Waltzing With Bears: Managing Risk on Software Projects
Purchase options and add-ons
By ignoring the threat of negative outcomesin the name of positive thinking or a Can-Do attitudesoftware managers drive their organizations into the ground.
In Waltzing with Bears, Tom DeMarco and Timothy Listerthe best-selling authors of Peoplewareshow readers how to identify and embrace worthwhile risks. Developers are then set free to push the limits.
You'll find that risk management
* makes aggressive risk-taking possible
* protects management from getting blindsided
* provides minimum-cost downside protection
* reveals invisible transfers of responsibility
* isolates the failure of a subproject.
Readers are taught to identify the most common risks faced by software projects:
* schedule flaws
* requirements inflation
* turnover
* specification breakdown
* and under-performance.
Packed with provocative insights, real-world examples, and project-saving tips, Waltzing with Bears is your guide to mitigating the risksbefore they turn into problems.
- ISBN-100932633609
- ISBN-13978-0932633606
- PublisherDorset House
- Publication dateJanuary 1, 2003
- LanguageEnglish
- Dimensions5.75 x 0.5 x 8.75 inches
- Print length144 pages
Discover the latest buzz-worthy books, from mysteries and romance to humor and nonfiction. Explore more
Frequently bought together

Customers who viewed this item also viewed
Editorial Reviews
Review
"Advice projects must not ignore (but often do) . . . A must for the project manager (and his or her boss)." -- Conrad Weisert, IDINews
"Bold, provocative yet coolly pragmatic . . ." -- Michael Schrage, Co-Director of MIT Media Lab s e-Markets Initiative, Author of Serious Play
"The book is a brilliant tour de force. . . . should be on your bookshelf . . . ." -- Paul Gray, Information Systems Management
"The seminal work on managing software project risk. . . . Finally we have a guide to risk management . . . ." -- Rob Austin, Professor, Harvard Business School
Product details
- Publisher : Dorset House
- Publication date : January 1, 2003
- Language : English
- Print length : 144 pages
- ISBN-10 : 0932633609
- ISBN-13 : 978-0932633606
- Item Weight : 10.4 ounces
- Dimensions : 5.75 x 0.5 x 8.75 inches
- Best Sellers Rank: #1,411,814 in Books (See Top 100 in Books)
- #162 in PMP Exam
- #1,579 in Software Development (Books)
- #3,737 in Computer Software (Books)
- Customer Reviews:
About the authors
Discover more of the author’s books, see similar authors, read book recommendations and more.
Tom DeMarco is the author of sixteen published books, including five novels, a collection of short stories, and the rest books about systems technology and the sociology of the workplace.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonTop reviews from the United States
There was a problem filtering reviews. Please reload the page.
- Reviewed in the United States on October 1, 2006Read this unsystematic and occasionally glib book (I concede this point to other reviewers) and you will suddenly realize that you, your colleagues in development, your technical leads, and your CEO have probably all been lying to yourselves and to each other about every single "milestone". Risk analysis is not merely done badly most of the time. It's usually not done at all. I learned enough from this book on a Sunday to return to work the next day and successfully persuade my colleagues that our project plan was worthless, and we needed to come up with a new one *now* that properly took account of the risks. No, I'm not a risk analyst, but merely the effort of thinking about risk in a different way had a payoff. Before this, we were just driving blind.
- Reviewed in the United States on June 24, 2014The book is great for anyone who wants to get structured thoughts around risk management. For seasoned program managers, it may not have much new; however, it walks one through the process. It also challenges you to look inside your organization to see what level of risk management is being followed, how to improve it and how to build accountability from all stakeholders involved (& not just development teams).
If you think you are an expert on software risk management, then perhaps you don't need to read this. Else, its a pretty good book to have,
- Reviewed in the United States on June 10, 2013very insightful, concise, and practical reading on understanding , and dealing with risks of software projects; the contents are universal and apply to projects of any size. a must read for product managers and project managers (who are not freakishly PMP-y).
- Reviewed in the United States on March 10, 2014In a lot of organizations risk management has become a burdensome process that simply slows everything down. DeMarco and Lister have done a terrific job creating a conscious and deliberate process that will create a practical amount of management while increasing the chances of actually delivering the project on time. This book should be a mandatory read for anyone managing moderate to high risk projects.
- Reviewed in the United States on August 27, 2015A great read, if a little heavy. But full of great information and views.
- Reviewed in the United States on September 27, 2003This book is an interesting mix. It starts with a philosophical discussion of why it is ethically wrong and success-endangering to ignore risks, but commercially weak to simply avoid them, thus establishing that we must accept and manage risk. The book then develops a comprehensive method for risk management in IT (or other) projects.
It may be surprising where DeMarco & Lister start from, explaining what risk is, why we need to accept it and why we must manage it, but they explain how common attitudes in the IT industry, which they correctly term "pathologies", can make it almost impossible to properly acknowledge and manage risks.
Maybe it's my background as a physicist, but I assumed that most project managers understand the concept of uncertainty in estimates of cost, timescale and benefits. The authors clearly start from the opposite position. This may be a little off-putting for some readers, but will definitely help those to whom this is a new concept, while the use of "uncertainty diagrams" (probability profiles) will be a useful addition to the toolkit even for those more familiar with the underlying ideas.
The book is very strong on how risk impacts budget and schedule, and how to more scientifically make goals and committed targets more realistic. There's a very good discussion of how to assess deadlines using probability theory, which shows the folly of trying to manage large efforts by single deadlines. The book also includes a very good section on brainstorming and analysing different stakeholders' "win" conditions to identify potential risks.
One weakness is the almost total lack of discussion of risk prevention - actively working to prevent a risk materialising, or at least to reduce its probability as well as mitigating its impact. For example they quote the example of an operating system upgrade which is incompatible with a "make or break" product development. Any sensible manager would work with the OS vendor and its developer information programmes to actively prevent this, rather than just worrying about its possible impact.
When it comes to combining the effects of multiple risks, the authors rely entirely on Monte-Carlo simulation and the "black box" outputs from a spreadsheet (which is downloadable from a web site for the book). This will be a useful tool, but a simple worked example showing the mathematical principles at work would be much better (see [...] risks.htm for my attempt at this).
The book is dismissive of time-constrained scheduling as "schedule flaw", and there is only limited consideration of methods such as Agile Modeling and eXtreme Programming which aim to mitigate or even prevent the effects of requirements change. However there is a good section on the use of incremental delivery to mitigate risk, but possibly somewhat unrealistic in relying on very complete requirements and design before the incremental delivery plan can be completed.
The approach to benefits, and the importance of properly assessing and measuring benefit is excellent. As DeMarco and Lister state, you can't do any meaningful risk management or prioritisation unless costs and benefits are estimated, measured and controlled to almost exactly the same degree. Conversely, if you can build realistic models of both cost and benefit in risk terms, you have a very powerful but relatively simple model for project prioritisation.
Overall this is a good book which I can recommend, but not the definitive answer I expected from the authors of "Peopleware".
Top reviews from other countries
- Mrs. AS GoodwinReviewed in the United Kingdom on March 29, 2009
5.0 out of 5 stars A Brilliant computer science textbook
I have tended to find that the smaller computer science textbooks are actually better than the inch thick that are more common. This is a very small book for CS but good things often come in small packages as with this book. If you want to know about software engineering in a short space of time then read this as opposed to Sommerville's Software Engineering mammoth tome.
- Raj MReviewed in Canada on November 28, 2019
5.0 out of 5 stars Risk Management
Good Book
-
TiggerReviewed in Germany on January 9, 2016
4.0 out of 5 stars Inhalt gut, Qualität des Einbandes mittel
Über den Inhalt kann ich nicht viel sagen, da es ein Geschenk war.
Der Einband ist von der Qualität nicht besonders hochwertig - die Ecken waren bei Lieferung auch abgestoßen. Der Umtausch ging zwar problemlos, aber hat nur wenig gebracht da auch das zweite Buch etwas mitgenommen aussah. Scheint generell an der Verarbeitung zu liegen. Der Preis erscheint hierfür sehr hoch.
- Stephan WiesnerReviewed in Germany on June 18, 2004
3.0 out of 5 stars nothing new
If you have read Deadline (DeMarco's best book by far), you will find nothing new.
Otherwise the book might be fun to read (if you don't have to pay the large price, which it clearly is not worth). Don't expect to do better risk management afterwards, though. Curves don't need to be 'nice and smooth' to make their point and his scientific methods are no better than an 'Nutzwertanalyse' (taking the average of a lot of guesses and thinking that this will result in an absolute measure of truth).
- Andrew JohnstonReviewed in the United Kingdom on September 27, 2003
4.0 out of 5 stars A good book covering an important and negelected area
This book is an interesting mix. It starts with a philosophical discussion of why it is ethically wrong and success-endangering to ignore risks, but commercially weak to simply avoid them, thus establishing that we must accept and manage risk. The book then develops a comprehensive method for risk management in IT (or other) projects.
It may be surprising where DeMarco & Lister start from, explaining what risk is, why we need to accept it and why we must manage it, but they explain how common attitudes in the IT industry, which they correctly term "pathologies", can make it almost impossible to properly acknowledge and manage risks.
Maybe it's my background as a physicist, but I assumed that most project managers understand the concept of uncertainty in estimates of cost, timescale and benefits. The authors clearly start from the opposite position. This may be a little off-putting for some readers, but will definitely help those to whom this is a new concept, while the use of "uncertainty diagrams" (probability profiles) will be a useful addition to the toolkit even for those more familiar with the underlying ideas.
The book is very strong on how risk impacts budget and schedule, and how to more scientifically make goals and committed targets more realistic. There's a very good discussion of how to assess deadlines using probability theory, which shows the folly of trying to manage large efforts by single deadlines. The book also includes a very good section on brainstorming and analysing different stakeholders' "win" conditions to identify potential risks.
One weakness is the almost total lack of discussion of risk prevention - actively working to prevent a risk materialising, or at least to reduce its probability as well as mitigating its impact. For example they quote the example of an operating system upgrade which is incompatible with a "make or break" product development. Any sensible manager would work with the OS vendor and its developer information programmes to actively prevent this, rather than just worrying about its possible impact.
When it comes to combining the effects of multiple risks, the authors rely entirely on Monte-Carlo simulation and the "black box" outputs from a spreadsheet (which is downloadable from a web site for the book). This will be a useful tool, but a simple worked example showing the mathematical principles at work would be much better (see [...] risks.htm for my attempt at this).
The book is dismissive of time-constrained scheduling as "schedule flaw", and there is only limited consideration of methods such as Agile Modeling and eXtreme Programming which aim to mitigate or even prevent the effects of requirements change. However there is a good section on the use of incremental delivery to mitigate risk, but possibly somewhat unrealistic in relying on very complete requirements and design before the incremental delivery plan can be completed.
The approach to benefits, and the importance of properly assessing and measuring benefit is excellent. As DeMarco and Lister state, you can't do any meaningful risk management or prioritisation unless costs and benefits are estimated, measured and controlled to almost exactly the same degree. Conversely, if you can build realistic models of both cost and benefit in risk terms, you have a very powerful but relatively simple model for project prioritisation.
Overall this is a good book which I can recommend, but not the definitive answer I expected from the authors of "Peopleware".