Home   FAQs   New Arrivals   Specials   Pricing & Shipping   Location   Corporate Services   Why Choose Bookware?  
 Search:   
Call our store: 9955 5567 (from within Sydney) or 1800 734 567 (from outside Sydney)
 View Cart   Check Out   
 
Browse by Subject
 TAFE Accounting
 TAFE I.T./Computing
 TAFE - Other
I.T
 .NET
 Windows 8
 Adobe CS6
 Cisco
 CCNA 2012
 CCNP 2012
 Java
 VB
 ASP
 Web Design
 E-Commerce
 Project Management
 ITIL
 Macintosh
 Mobile Devices
 Linux
 Windows Server 2012
 SQL Server 2012
 SAP
Certification
 MCITP
 MCTS
Economics and Business
 Accounting
 Business Information Systems
 Economics
 Finance
 Management
 Marketing
 TAX
 Human Resources
Academic
 Law
 Nursing
 Medical
 Psychology
 Engineering

Death March - 2nd edition

by: Edward Yourdon

Notify me when in stock

On-line Price: $39.95 (includes GST)

Paperback package 256

20%Off Retail Price

You save: $10.00

Usually ships within 4 - 5 business days.
_____________________
N.Sydney : On Order (reserve your copy)

Retail Price: $49.95

Publisher: PRENTICE HALL PTR,2003/11/06

Category: PROJECT MANAGEMENT Level: I/A

ISBN: 013143635X
ISBN13: 9780131436350

Add to Shopping Cart

Summary


      Death March

Second Edition

The #1 guide to surviving 'doomed' projects...Fully updated and expanded, with powerful new techniques!


  At an alarming rate, companies continue to create death-march projects, repeatedly! What's worse is the amount of rational, intelligent people who sign up for a death-march projectsaeprojects whose schedules, estimations, budgets, and resources are so constrained or skewed that participants can hardly survive, much less succeed. In Death March, Second Edition, Ed Yourdon sheds new light on the reasons why companies spawn Death Marches and provides you with guidance to identify and survive death march projects.


  Yourdon covers the entire project lifecycle, systematically addressing every key issue participants face: politics, people, process, project management, and tools. No matter what your role--developer, project leader, line-of-business manager, or CxO--you'll find realistic, usable solutions. This edition's new and updated coverage includes:


  Creating Mission Impossible projects out of DM projects

Negotiating your project's conditions: making the best of a bad situation

XP, agile methods, and death march projects

Time management for teams: eliminating distractions that can derail your project

'Critical chain scheduling': identifying and eliminating organizational dysfunction

Predicting the 'straw that breaks the camel's back': lessons from system dynamics

Choosing tools and methodologies most likely to work in your environment

Project 'flight simulators': wargaming your next project

Applying triage to deliver the features that matter most

When it's time to walk away

This isn't a book about perfectly organized projects in 'textbook' companies. It's about your project, in your company. But you won't just recognize your reality: you'll learn exactly what to do about it.


          Author Bio


      EDWARD YOURDON has been called one of the ten most influential people in software, and has been inducted into the Computer Hall of Fame alongside Charles Babbage, Seymour Cray, James Martin, Grace Hopper, and Bill Gates. An internationally recognized consultant, he is author or coauthor of more than 25 books, including Byte Wars, Managing High-Intensity Internet Projects, and Decline and Fall of the American Programmer. He co-developed the popular Coad/Yourdon methodology, co-founded the influential Cutter Consortium Business Technology Council, and serves on the Board of Directors of iGate and Mascot Systems.


      

Table of Contents

Preface.


      1. Introduction.


      Death March Defined.


      Categories of Death March Projects.


      Why Do Death March Projects Happen?


      Politics, Politics, Politics.


      Naive Promises Made by Marketing, Senior Executives, Naive Project Managers, and So on.


      Naive Optimism Of Youth: 'We Can Do It Over the Weekend'.


      The 'Startup' Mentality of Fledgling Entrepreneurial Companies.


      The 'Marine Corps' Mentality: Real Programmers Don't Need Sleep.


      Intense Competition Caused by Globalization of Markets.


      Intense Competition Caused by the Appearance of New Technologies.


      Intense Pressure Caused by Unexpected Government Regulations.


      Unexpected and/or Unplanned Crises.


      Why Do People Participate in Death March Projects?


      The Risks Are High, but So Are the Rewards.


      The 'Mt Everest' Syndrome.


      The Naiveté and Optimism of Youth.


      The Alternative Is Unemployment.


      It's Required in Order to Be Considered for Future Advancement.


      The Alternative Is Bankruptcy or Some Other Calamity.


      It's an Opportunity to Escape the 'Normal' Bureaucracy.


      Revenge.


      Summary.


      Notes.


          2. Politics.


      Identifying the Political Players in the Project.


      Owner.


      Customers.


      Shareholders.


      Stakeholders.


      Champions.


      Determining the Basic Nature of the Project.


      Levels of Commitment by Project Participants.


      Analyzing Key Issues that Lead to Political Disagreements.


      Conclusion.


      Notes.


          3. Negotiations.


      Rational Negotiations.


      Identifying Acceptable Tradeoffs.


      Negotiating Games.


      Negotiating Strategies.


      What To Do When Negotiating Fails.


      Notes.


      References.


          4. People in Death March Projects.


      Hiring and Staffing Issues.


      Loyalty, Commitment, Motivation, and Rewards.


      Rewarding Project Team Members.


      The Issue of Overtime.


      The Importance of Communication.


      Team-Building Issues.


      Workplace Conditions for Death March Project.


      Summary.


      Notes.


      References.


          5. Death March Processes.


      The Concept OF Triage.


      The Importance OF Requirements Management.


      SEI, ISO-9000 and Formal Versus Informal Processes.


      Good-Enough Software.


      Best Practices and Worst Practices.


      Death March Meets XP.


      Conclusion.


      Notes.


      References.


          6. The Dynamics of Processes.


      Models of Software Development Processes.


      Mental Models.


      Spreadsheet Models.


      Static Versus Dynamic Models.


      Visual Models.


      An Example: Tarek Abdel-Hamid's Software Process Model.


      Summary and Conclusions.


      Notes.


      References.


          7. Critical-Chain Scheduling and the Theory of Constraints.


      Introduction.


      What Organizational Behaviors are Dysfunctional?


      How Can We Change Dysfunctional Organizational Behavior?


      Life in a Rational World.


      Critical-Chain Scheduling.


      Conclusion.


      Notes.


      References.


          8. Time Management.


      The Impact of Corporate Culture On Time Management.


      Time Slippage from Stakeholder Disagreements.


      Helping the Project Team Make Better Use of Time.


      Notes.


          9. Managing and Controlling Progress.


      The 'Daily Build' Concept.


      Risk Management.


      Additional Ideas for Monitoring Progress: Milestone Reviews.


      Notes.


      References.


          10. Death March Tools and Technology.


      The Minimal Toolset.


      Tools and Process.


      Risks of Choosing New Tools.


      Conclusion.


      Notes.


      References.


          11. Simulators and 'War Games'.


      Introduction.


      The Concept of War Games.


      Conclusion.


      Notes.


      References.


          Index.