- Save $10 when you spend $50 and pay with Bill Me Later. The fast and convenient way to buy without using your credit card. Offer limited to items purchased from Amazon.com between July 14, 2008 and July 21, 2008. One per customer account. Enter code BMLSAVES at checkout. Here's how (restrictions apply)
Join Amazon Prime and ship Two-Day for free and Overnight for $3.99. Already a member? Sign in.
|
|||||||||||||
Special Offers and Product Promotions
Better Together
Customers Who Bought This Item Also Bought
Peopleware: Productive Projects and Teams (Second Edition) by Tom DeMarco  (77)
$33.95
|
Waltzing With Bears: Managing Risk on Software Projects by Tom DeMarco  (23)
$25.16
|
Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency by Tom DeMarco  (38)
$10.17
|
Software Estimation: Demystifying the Black Art (Best Practices (Microsoft)) by Steve McConnell (32)
$26.39
|
Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software by Scott Rosenberg (61)
$11.16
|
Editorial Reviews
Amazon.com
Death march projects are becoming increasingly common in the software industry. The symptoms are obvious: The project schedule, budget, and staff are about half of what is necessary for completion. The planned feature set is unrealistic. People are working 14 hours a day, six or seven days a week, and stress is taking its toll. The project has a high risk of failure, yet management is either blind to the situation or has no alternative. Why do these irrational projects happen, and what, other than pure idiocy, leads people to get involved in them?
Death march projects are becoming increasingly common in the software industry. The symptoms are obvious: The project schedule, budget, and staff are about half of what is necessary for completion. The planned feature set is unrealistic. People are working 14 hours a day, six or seven days a week, and stress is taking its toll. The project has a high risk of failure, yet management is either blind to the situation or has no alternative. Why do these irrational projects happen, and what, other than pure idiocy, leads people to get involved in them?
Edward Yourdon has produced a wise and highly readable book on the entire death march phenomenon and the best way to steer through one. He takes a close look at the types of projects that often become death marches and the corporate politics and culture that typically produce them; Yourdon helps you examine your own motivations and those of corporate managers who enable death marches to take shape.
Much of Death March is about the human element of highly stressful projects. The author's plain-spoken observations on the dysfunctional organization--the Machiavellian politics, naive optimism, lust for power, fear, and sheer managerial stupidity that guide so many death marches--make for a refreshing change from other project management books. You'll also find much practical advice to help you survive, everything from negotiating with upper management to breathing life into faltering projects. He'll even help you determine if you should look for another job.
If you've ever worked in a death march situation or been a client of a company addicted to death march management, this book will help you understand what happened. More importantly, it will help you prepare for future encounters with death marches. Death March is highly recommended for anyone involved in software development.
--This text refers to an out of print or unavailable edition of this title.
Book Info
Presents specific techniques for: Managing people and teams, Choosing the right processes, Making decisions about tools and technologies, Setting priorities, and Getting the flexibility you need to succeed. DLC: Computer software - Development.
--This text refers to an out of print or unavailable edition of this title.
See all Editorial Reviews
Product Details
|