<?xml version="1.0" encoding="UTF-8"?>
<GoodreadsResponse>
	<Request>
		<authentication>false</authentication>
		    <method><![CDATA[]]></method>
	</Request>
	
<book>
  <id>447995</id>
  <title><![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]></title>
  <isbn><![CDATA[0130146595]]></isbn>
  <isbn13><![CDATA[9780130146595]]></isbn13>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <description><![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]></description>
  <work>
  <best_book_id type="integer">447995</best_book_id>
  <books_count type="integer">1</books_count>
  <desc_user_id type="integer" nil="true"></desc_user_id>
  <id type="integer">436655</id>
  <media_type nil="true"></media_type>
  <original_language_id type="integer" nil="true"></original_language_id>
  <original_publication_day type="integer" nil="true"></original_publication_day>
  <original_publication_month type="integer" nil="true"></original_publication_month>
  <original_publication_year type="integer">1999</original_publication_year>
  <original_title>Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)</original_title>
  <rating_dist>total:17|5:5|4:5|3:4|2:2|1:1|</rating_dist>
  <ratings_count type="integer">17</ratings_count>
  <ratings_sum type="integer">62</ratings_sum>
  <reviews_count type="integer">36</reviews_count>
  <text_reviews_count type="integer">4</text_reviews_count>
</work>

  <average_rating><![CDATA[3.65]]></average_rating>
  <ratings_count><![CDATA[17]]></ratings_count>
  <text_reviews_count><![CDATA[4]]></text_reviews_count>
  
  <url><![CDATA[http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects]]></url>
  <link><![CDATA[http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects]]></link>
  <authors>
    <author>
    <id>30682</id>
        <name><![CDATA[Edward Yourdon]]></name>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-200x266.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto/nophoto-U-50x66.jpg]]></small_image_url>
    <link><![CDATA[http://www.goodreads.com/author/show/30682.Edward_Yourdon]]></link>
    <average_rating>3.42</average_rating>
    <ratings_count>74</ratings_count>
    <text_reviews_count>14</text_reviews_count>
  </author>
  </authors>
    <reviews start="1" end="20" total="36">
      <review>
  <id>76905793</id>
    <user>
    <id>2619204</id>
    <name><![CDATA[Marni]]></name>
    <location><![CDATA[Dunedin, E7, New Zealand]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2619204-marni]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-F-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-F-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>3</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Fri Nov 06 00:00:00 -0800 2009</read_at>
  <date_added>Fri Nov 06 07:10:08 -0800 2009</date_added>
  <date_updated>Fri Nov 06 14:25:31 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[I have read the Polish edition:<br/><a rel="nofollow" target="_blank" href="http://atena.osdw.pl/ksiazka/Yourdon-Edward/Marsz-ku-klesce,43822901007KS" title="http://atena.osdw.pl/ksiazka/Yourdon-Edward/Marsz-ku-klesce,43822901007KS">http://atena.osdw.pl/ksiazka/Yourdon-Edw...</a><br/><a rel="nofollow" target="_blank" href="http://a.swistak.pl/000/326/326955_1024.jpg" title="http://a.swistak.pl/000/326/326955_1024.jpg">http://a.swistak.pl/000/326/326955_1024....</a><br/><br/>Good book, but I've read the 1999 edition, and felt some of the issues were a bit outdated. Lots of good suggestions and analysis that is still valid. <a href="http://www.goodreads.com/review/show/76905793">more...</a>]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/76905793]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/76905793]]></link>
</review>
      <review>
  <id>26824447</id>
    <user>
    <id>732709</id>
    <name><![CDATA[mlady_rebecca]]></name>
    <location><![CDATA[Owings Mills, MD]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/732709-mlady-rebecca]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1199345526p3/732709.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1199345526p2/732709.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="2001" />
        <shelf name="non-fiction__engineering" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at>Wed Aug 01 00:00:00 -0700 2001</read_at>
  <date_added>Wed Jul 09 22:00:49 -0700 2008</date_added>
  <date_updated>Thu Aug 07 19:45:39 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[I read this the year I lived a death march project. Essentially, that's a project where you have too little resources in terms of time or personnel. Ironically, it was the most fun project of my career. We went down, but we went down together and in good spirits. ]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/26824447]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/26824447]]></link>
</review>
      <review>
  <id>13452057</id>
    <user>
    <id>715998</id>
    <name><![CDATA[Alan]]></name>
    <location><![CDATA[Gaithersburg, MD]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/715998-alan]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1252071895p3/715998.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1252071895p2/715998.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>4</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="computers" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Jan 24 17:39:04 -0800 2008</date_added>
  <date_updated>Sat Feb 16 12:54:41 -0800 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[Ever been on a big computer project?  It may not be Death March but it sometimes feels like the Lost Battalion.  ]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/13452057]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/13452057]]></link>
</review>
      <review>
  <id>3995713</id>
    <user>
    <id>247193</id>
    <name><![CDATA[Will]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/247193-will]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1186110891p3/247193.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1186110891p2/247193.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>1</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Aug 02 18:31:30 -0700 2007</date_added>
  <date_updated>Thu Dec 17 03:29:31 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[Tedious and repetitive, no useful info.]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/3995713]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/3995713]]></link>
</review>
      <review>
  <id>69396933</id>
    <user>
    <id>2344451</id>
    <name><![CDATA[Cort]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2344451-cort]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-U-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="joel-spolsky-recommendations" />
        <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Aug 29 20:28:00 -0700 2009</date_added>
  <date_updated>Sun Aug 30 16:39:54 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/69396933]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/69396933]]></link>
</review>
      <review>
  <id>66070387</id>
    <user>
    <id>1090057</id>
    <name><![CDATA[Peter]]></name>
    <location><![CDATA[San Diego, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1090057-peter]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1219633324p3/1090057.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1219633324p2/1090057.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Aug 03 17:58:41 -0700 2009</date_added>
  <date_updated>Mon Aug 03 17:58:41 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/66070387]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/66070387]]></link>
</review>
      <review>
  <id>63621546</id>
    <user>
    <id>1785889</id>
    <name><![CDATA[Ben!]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1785889-ben]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1228790591p3/1785889.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1228790591p2/1785889.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Jul 15 13:17:48 -0700 2009</date_added>
  <date_updated>Wed Jul 15 13:17:48 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/63621546]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/63621546]]></link>
</review>
      <review>
  <id>61616649</id>
    <user>
    <id>527217</id>
    <name><![CDATA[Garrett]]></name>
    <location><![CDATA[The United States]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/527217-garrett]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1192726402p3/527217.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1192726402p2/527217.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Jun 30 07:26:32 -0700 2009</date_added>
  <date_updated>Tue Jun 30 07:26:32 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/61616649]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/61616649]]></link>
</review>
      <review>
  <id>52654841</id>
    <user>
    <id>711169</id>
    <name><![CDATA[Bek]]></name>
    <location><![CDATA[Tallahassee, FL]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/711169-bek]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1210378406p3/711169.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1210378406p2/711169.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Apr 14 11:14:15 -0700 2009</date_added>
  <date_updated>Tue Apr 14 11:14:15 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/52654841]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/52654841]]></link>
</review>
      <review>
  <id>52197880</id>
    <user>
    <id>991542</id>
    <name><![CDATA[Rich]]></name>
    <location><![CDATA[Germantown, MD]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/991542-rich]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1206114606p3/991542.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1206114606p2/991542.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>2</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Fri Apr 10 10:21:47 -0700 2009</date_added>
  <date_updated>Fri Apr 10 10:21:47 -0700 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/52197880]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/52197880]]></link>
</review>
      <review>
  <id>47497021</id>
    <user>
    <id>2071802</id>
    <name><![CDATA[Simon]]></name>
    <location><![CDATA[Ottawa, NY, Canada]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/2071802-simon-macdonald]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1235588411p3/2071802.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1235588411p2/2071802.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Wed Feb 25 10:34:04 -0800 2009</date_added>
  <date_updated>Wed Feb 25 10:34:04 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/47497021]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/47497021]]></link>
</review>
      <review>
  <id>44910484</id>
    <user>
    <id>1822428</id>
    <name><![CDATA[Richard]]></name>
    <location><![CDATA[Ottawa, Canada]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1822428-richard]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1229909231p3/1822428.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1229909231p2/1822428.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Fri Jan 30 18:58:01 -0800 2009</date_added>
  <date_updated>Fri Jan 30 18:58:01 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/44910484]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/44910484]]></link>
</review>
      <review>
  <id>43570042</id>
    <user>
    <id>1889506</id>
    <name><![CDATA[Wesen]]></name>
    <location><![CDATA[Weimar, 01, Germany]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1889506-wesen]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1255422109p3/1889506.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1255422109p2/1889506.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>3</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Mon Jan 19 08:20:05 -0800 2009</date_added>
  <date_updated>Mon Jan 19 08:20:05 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/43570042]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/43570042]]></link>
</review>
      <review>
  <id>40768076</id>
    <user>
    <id>1193822</id>
    <name><![CDATA[Joseph]]></name>
    <location><![CDATA[Denver, CO]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1193822-joseph]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1212004393p3/1193822.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1212004393p2/1193822.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Dec 23 11:36:43 -0800 2008</date_added>
  <date_updated>Tue Dec 23 11:36:43 -0800 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/40768076]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/40768076]]></link>
</review>
      <review>
  <id>37170939</id>
    <user>
    <id>1404571</id>
    <name><![CDATA[Egor]]></name>
    <location><![CDATA[Sydney, Australia]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1404571-egor-pervuninski]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1218711570p3/1404571.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1218711570p2/1404571.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="management" />
        <shelf name="owned" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Nov 08 03:42:10 -0800 2008</date_added>
  <date_updated>Sat Nov 08 03:42:22 -0800 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/37170939]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/37170939]]></link>
</review>
      <review>
  <id>35484508</id>
    <user>
    <id>1627733</id>
    <name><![CDATA[Ray]]></name>
    <location><![CDATA[Ishpeming, MI]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1627733-ray]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1224200420p3/1627733.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1224200420p2/1627733.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>5</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Thu Oct 16 13:26:22 -0700 2008</date_added>
  <date_updated>Thu Oct 16 13:26:22 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/35484508]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/35484508]]></link>
</review>
      <review>
  <id>32452369</id>
    <user>
    <id>1512378</id>
    <name><![CDATA[Jim]]></name>
    <location><![CDATA[Sutton Coldfield, The United Kingdom]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1512378-jim-dabell]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Sep 09 12:07:05 -0700 2008</date_added>
  <date_updated>Tue Sep 09 12:07:05 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/32452369]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/32452369]]></link>
</review>
      <review>
  <id>30300679</id>
    <user>
    <id>1298864</id>
    <name><![CDATA[Jordan]]></name>
    <location><![CDATA[Raleigh, NC]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1298864-jordan]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1218897441p3/1298864.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1218897441p2/1298864.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
            <shelf name="to-read" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Aug 16 07:39:11 -0700 2008</date_added>
  <date_updated>Sun Dec 13 06:55:50 -0800 2009</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/30300679]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/30300679]]></link>
</review>
      <review>
  <id>25329615</id>
    <user>
    <id>1266455</id>
    <name><![CDATA[André]]></name>
    <location><![CDATA[San Jose, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1266455-andr-levy]]></link>
    <image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-111x148.jpg]]></image_url>
    <small_image_url><![CDATA[http://www.goodreads.com/images/nophoto-M-50x66.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
          </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Tue Jun 24 12:19:21 -0700 2008</date_added>
  <date_updated>Tue Jun 24 12:19:21 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/25329615]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/25329615]]></link>
</review>
      <review>
  <id>23914955</id>
    <user>
    <id>1012885</id>
    <name><![CDATA[Joe]]></name>
    <location><![CDATA[Lemon Grove, CA]]></location>
    <link><![CDATA[http://www.goodreads.com/user/show/1012885-joe]]></link>
    <image_url><![CDATA[http://photo.goodreads.com/users/1206134866p3/1012885.jpg]]></image_url>
    <small_image_url><![CDATA[http://photo.goodreads.com/users/1206134866p2/1012885.jpg]]></small_image_url>
  </user>
    <book>
  <id type="integer">447995</id>
  <isbn>0130146595</isbn>
  <isbn13>9780130146595</isbn13>
  <text_reviews_count type="integer">4</text_reviews_count>
  <title>
    <![CDATA[Death March: The Complete Software Developer's Guide to Surviving 'Mission Impossible' Projects (Yourdon Computing Series)]]>
  </title>
  <image_url>http://photo.goodreads.com/books/1174862184m/447995.jpg</image_url>
  <small_image_url>http://photo.goodreads.com/books/1174862184s/447995.jpg</small_image_url>
  <link>http://www.goodreads.com/book/show/447995.Death_March_The_Complete_Software_Developer_s_Guide_to_Surviving_Mission_Impossible_Projects</link>
  <average_rating>3.65</average_rating>
  <ratings_count>17</ratings_count>
  <description>
    <![CDATA[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?<p>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.<p> Much of <em>Death March</em> 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.<p> 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. <em>Death March</em> is highly recommended for anyone involved in software development.</p></p></p>]]>
  </description>
  <published>1999</published>
</book>

    <rating>0</rating>
  <votes>0</votes>
  <spoiler_flag>false</spoiler_flag>
  <shelves>
        <shelf name="read" />
            <shelf name="software-development" />
      </shelves>
  <recommended_for><![CDATA[]]></recommended_for>
  <recommended_by><![CDATA[]]></recommended_by>
  <read_at></read_at>
  <date_added>Sat Jun 07 04:24:13 -0700 2008</date_added>
  <date_updated>Sat Jun 07 04:24:13 -0700 2008</date_updated>
  <read_count></read_count>
    <body><![CDATA[]]></body>
    
  <url><![CDATA[http://www.goodreads.com/review/show/23914955]]></url>
  <link><![CDATA[http://www.goodreads.com/review/show/23914955]]></link>
</review>
    </reviews>
  <popular_shelves>
          <shelf name="to-read" />
          <shelf name="computers" />
          <shelf name="joel-spolsky-recommendations" />
          <shelf name="2001" />
          <shelf name="tech" />
          <shelf name="management" />
          <shelf name="technical" />
          <shelf name="software-development" />
          <shelf name="project-management" />
      </popular_shelves>
  <book_links>
    <book_link>
  <id>8</id>
  <name><![CDATA[WorldCat]]></name>
  <link>http://www.goodreads.com/book_link/follow/8?book_id=447995</link>
</book_link>
  </book_links>
</book>
</GoodreadsResponse>