Death journey 2nd

If you read this book as a universal soft work book such as agile software development, and want to find some suggestions that will benefit your daily projects, you will not get anything.
Because this book only teaches people how to adopt conservative and pragmatic strategies, "there is no harm to a dead-end project ".

This is an interesting topic.

Because death-based projects are generally ugly, few books will summarize the "best practices" here ". We are more willing to discuss on the basis of normal projects and guide you through "best practices" to avoid falling into the embarrassing field of death.
Unfortunately, the death journey project is still full of our surroundings, and every past death journey project is only used as the memory of the participants. This book reminds you that it is very important to summarize the "best practices" of normal projects so that you can complete tasks better, summarizing the "best practices" of the Death journey project teaches you how to survive the project as much as possible.
However, there may be different ways for everyone to die. A Guide to survival cannot save the world. When you think of yourself, you should sum up this book to achieve the goal of 50%.

I. Politics, politics, and Politics
Politics, players, and negotiation. ItProgramPersonnel may not be very good at these fields, but many deaths are actually due to politics. A good negotiation can reverse the overall project situation, the effect is much higher than the overtime work for N days and N nights. Therefore, programmers should also pay attention to the basic political and negotiation skills to prepare for war.
The American-style politics in the book is of course very different from that of Chinese characteristics, but when we get started, we can figure it out on our own.

Ii. Conservative and pragmatic
The project of the Death journey is the highest goal in the past. If it still carries the technical fanaticism and heroism in normal projects, it will surely die even worse.
Team building: You must use real-time candidates. Do not think that sandbags can be converted during the project. Unsuitable personnel, first of all, cannot be included in the project as a soldier. If it is hard to be included, let him do what he can, idle or go to the photocopier, you don't have to worry about training, let alone arrange experts to accompany you.
Selection of tools, technologies, and software processes:
Do not try any new technologies (unless required in the contract), use the most comfortable development environment, the simplest technology.
1. Try not to use items not trained in the team
2. Try not to use C/C ++/Smalltalk/lisp/artificial intelligence
3. Try to stay in windows and do not use Unix or other systems.
4. Try to use the WYSIWYG Development Environment

Iii. Demand Management
In the same way as XP and RUP, the author emphasizes that the demand priority should be distinguished and the requirements with low priority should be postponed or canceled through negotiation.
In a separate OOAD methodology, there are no requirements priorities and requirement change records.

4. Others
There are too many lines in the book.

Reading soft work books is the most important thing to think about. Otherwise, you will soon finish reading the books and forget them. In particular, the foreign situations are different from us.