Death March (Yourdon Press Computing Series)
| Author | : | |
| Rating | : | 4.19 (964 Votes) |
| Asin | : | 0137483104 |
| Format Type | : | paperback |
| Number of Pages | : | 227 Pages |
| Publish Date | : | 2013-09-05 |
| Language | : | English |
DESCRIPTION:
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. People are working 14 hours a day, six or seven days a week, and stress is taking its toll. Death march projects are becoming increasingly common in the software industry. More importantly, it will help you prepare for future encounters with death marches. The planned feature set is unrealistic. . You'll also find much practical advice to help you survive, everything from negotiating with upper management to breathing life into faltering projects. He takes a clos
Andrew Clay said It is a Death March to read. I couldn't finish it. I bought it because I was hooked on the author back in the early 80's and thought he was a genius. Maybe he should stick to pure textbooks. This was like a Death March, trying to read it. You know something is wrong when you are just trying to 'get through it'. I was looking for solutions to projects that become a Death March, peppered with anecdotes. I guess I'm too myopic for my own good. I couldn't believe one of his suggestions was to . not that much useful information. Greg Marsh The cover of the books reads "The Complete Software Developer's Guide to Surviving "Mission Impossible" Projects. The inside flap reads "Managing "Mission Impossible" Projects. Definition of software developer - a person concerned with facets of the software development process, including the research, design, programming, and testing of computer software. I think the book's cover should be reworded to, Death March The Complete Software PROJECT MANAGER Guide to. Your latest horror project was no coincidence but there are Prlwrlczkwsky Your latest horror project was no coincidence but there are systemic reasons that let projects gravitate towards disaster.And because of these systemic causes, there is a chance for preemptive actions.This book describes the pain and the learning from the pain.Read it and pass it on - as I did.
*Choosing tools and technologies. If you've ever been asked to do the impossible, Death March is the book you've been waiting for.. 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 to simply walk away. 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. *When it's time to walk away. *Managing people and setting priorities. 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 noth