Click on a thumbnail to go to Google Books.
Loading... Death march (1997)by Edward Yourdon
None Loading...
Sign up for LibraryThing to find out whether you'll like this book. No current Talk conversations about this book. Tedious and repetitive, no useful info. ( ) If you are working at a place that believes in the Death March, you owe it to yourself to find time to read this book (not an easy thing when you are working 14 hours a day, seven days a week). If you have never worked at such a place, you should at least skim the book to understand why you don't want to work for such an employee. If you've survived a death march and now work at a saner company, you don't need this book in the least. Word of warning: it is depressing to read this book and then see your employer is a textbook example of how not to run a software company. Knowing what would happen, I scheduled a meeting with my manager and brought in the book with little sticky-notes on key pages. I then cataloged what the company was doing wrong and why it was bad. They fired me, of course. In a month I was working for a fantastic start-up. I've been at that firm for five years now. We work hard, but we do not do death marches. That other company? Dead and gone. no reviews | add a review
The complete software developer's guide to surviving projects that are 'doomed to fail.' In the course of a career, practically every software developer and manager will encounter projects with outrageous staffing, scheduling, budgeting, or feature constraints: projects that seem destined to fail. In the wake of re-engineering, such 'Death March' projects have become a way of life in many organizations. * Surviving projects that are 'doomed to fail' * Negotiating the best deal up-front. * Managing people and setting priorities. * Choosing tools and technologies. * When it's time to walk away. Now, best-selling author Edward Yourdon brings his unique technology and management insights to the worst IS projects, showing how to maximize your chances of success-and, if nothing else, how to make sure your career survives them. Yourdon walks step-by-step through the entire project life cycle, showing both managers and developers how to deal with the politics of 'Death March' projects-and how to make the most of the available resources, including people, tools, processes, and technology. Learn how to negotiate for the flexibility you need, how to set priorities that make sense-and when t No library descriptions found. |
Current DiscussionsNonePopular covers
Google Books — Loading... GenresMelvil Decimal System (DDC)005.1068Information Computer Science; Knowledge and Systems Computer programming, programs, data, security Programming Programming -- Subdivisions Business & Organizations ManagementLC ClassificationRatingAverage:
Is this you?Become a LibraryThing Author. |