Listening to some views of this book, I don't agree with the content of the book he appreciated and turned into. So I went to the bookstore for a lot of books yesterday. I feel that his transcripts and the understanding of the book are all right, that is, I don't have the point of view in the book.
Reading is exciting, but it feels that the author is too desirable to develop. The work of project development, I thought it was divided into two categories. A type is to focus on the project process itself, and a class is the participant in the main investigation project. In the former, I thought as "Month", the latter, such as "last deadline" (I think "person" should be also). A good work should be a limitation in the actual environment and consider the appropriate strategy on the basis of the actual limitations. But "adaptive" seems to be more like a lot of inspirational reading on the market, and it will encourage yourself, can't be true. Especially when you develop a large application rather than the product.
The system points out that my opinion is somewhat difficult. Excerpt some views for your reference.
One is to emphasize that the team members should maintain a high degree of active open mental adaptation. I feel that the big premise is not wrong. But long-term fierce changes is indeed the best way to dissipate the team members. The "Term" said: The person under pressure cannot think very well. A fierce change is indeed a good way to generate pressure. I can't expect my group members to maintain this mentality in the development process of more than 6 months, I can't do it. This is the reality of most project groups.
Second, it feels that the customer's demand will eventually converge, so there is always a bitter day. I also thought I didn't. I believe that many people have experienced changes in customer demand, many are not very rational, and even a lot is going to fall. There are a lot of modifications that are meaningful in programmers (including post-proven), but it seems important at the time of the customer business, and the team can only be succumbed. This is also the killer of the group morale.
The third is about enterprises transformation, the authors are very simple, and the old total use of paper pen. I am amazing how to do it, the author took an example of MS. This is nothing to say, how many people do people learn? SUN, HP, Dell, etc. don't come. The author then refers to Microsoft's reasons to do so, such as mature values and superior leaders. It can be seen that this and the so-called adaptive method is not big. There is a famous saying in the industry: ask where 500 pounds of orangutans sleep? The answer is: Where is it, where is it. What is the industry leader thinks? As for the successor of learning, it is the shortcut of our success. This topic is even greater, and it is interested in discussing.
The fourth is to emphasize that small-scale products developed in this approach can be put into use, produce benefits. This method has certain feasibility, and I do the data analysis project is also a similar practice. But in general, I basically disagree, especially from the large business system I have, I will not be feasible. The problem is not that the development group can be done, but for such a user, it is very laborious for training and promotion of a business person. The promotion of the new software is not used to buy a table. The promotion of business software often means that the business is re-integrated, the risk is very large (even the author of the "period" only dares to lift the product), this is not a lot of tossing.
The fifth is a bit ignored the role of politics. This problem is relatively large, but I think the development of big projects must be considered. The third and fourth points above are also related to politics. The Bello Minister in the Termination is a representative of political impact, and this pressure in reality will come from its own leadership and customer leadership. The characters in the novel were solved, but in the actual project could not be clear. The author of the "Term" also said: The miracle will appear, but don't hold too much hope (most of this).
There are still many, take these. The total feelings are a bit idealized, compared to the author of the "Month", "deadline", is much more reality. Interested people can look at these works.
I have always had such a point of view: I don't have to face the final user is the happiest, just like a person who abroad is coming back: or the motherland of socialism is good. My feeling, the author seems to be a person who has not facing the application of the project torture. There is a doubt: the author distinguishes between spiral development and so-called adaptive development, I seem to see a big difference. Does anyone have an in-depth view?
By the way: The author is an advisory experience than actual project managers, and the book is mad 1999. Of course, this is not an argument on the content of the judgment, but I am sure that I have a Lenovo after my opinion. Ha ha
Personally see, someone is laughing. I am not ready to buy this book, I am waiting for "person".
