Bear Day: I have a question from the audience from the following, and this problem is very interesting, and also is related to Professor Lin. It is said that Professor Lin said such a saying: "UP is Zhengwei, XP is a history, first use XP and use UP will mess up." Let's ask Professor Lin to explain.
Professor Forest: I will translate in English first (Speak in english). Welcome, you are called Godfather. We have been waiting for your speech for a year. We are very regrettable to miss you a year.
Martin: I promise that I very much hope that I can do that time in the hotel.
Professor Lin: Interesting is "Godfather" to think about it over and over again. We have worked in the software industry for many years. We are from C , to Java ... All these languages have experienced a long time. Godfather introduces to our different languages. But from the software owner of this type of education, we accept UML and CMM from RUP. People hope to be very strictly implemented, and it is not easy to achieve it. Some people are thinking, why most methodologies come from the United States. Many people learn from the traditional method, go to the agile, and to limit programming, what is the reason? I have to ask you.
Martin: I don't think most of this transformation now, and changes come from the United States. Why is agile true to pay attention? I think it is because of the process of learning. When people get a large heavy way, they are not willing to use. When you go to the IBM Global Services, they will give you a lot of documents, but there is no real product. In addition, we have found that there will still be out of control. Sometimes, we will realize that the project is extended very late. Another feature of heavy-duty methodology is that it attracts the development of traditional engineering and believes that software development is expected to be accurate. Tell developers what you need, it takes a product for a few years. This is ok when it is in an ideal state. However, things are not as imagined. Therefore, we have learned. Some methods and practices guided in heavy methods should not be used. So we need to find new ways. When you go to explore, you don't know where you go, is it close to the end, we are in this way of exploring the methodology of agile process. I am very fortunate to be in a company with agile methods. But now we have seen a lot of changes. I am still in such a research process now, and the way we are now doing projects have been different from three years ago. I believe that in a few years, there will be a different change. Sometimes, people will talk about a few years ago, and then how terrible projects are that, how bad they work. I think this is a good thing, because you can see that you have learned a lot. You can look at the code you wrote in five years. If you can't understand it, this is not a good thing.
Professor Forest: Very good. I have worked in the United States for many years. At that time, there were about 75% of the projects failed, especially C . Do you agree?
Martin: Because many people have very different definitions on the word "failure", I am too tricky. Software has a lot of different divisions, many people fail in traditional planned driver, because they exceed budget. In the agile method, we look at failed in different ways. If the item is not delivered (to the customer), then it is failed. So a project may be postponed, exceeding the budget, but it delivers value to customers; it may be on time, completed within the budget, but did not deliver value to customers. These two definitions are different. Most of the projects are disappointing, we can do better. Most of the projects we can do some of our practices, making it better. We are committed to this industry, hoping to promote its development. Professor Lin: Is there any problem? (Start answering questions about orthodoxicle and grassbooks) Now Martin Fowler is here a very important moment. I always feel that the students of our Software Academy can think about a problem. Why is these people have been strictly trained in her early years, and the books written are about UML. You can't criticize them, they don't understand these very stringent things, they are themselves UML expert. However, the whole thoughts are now turned to XP, this is worth thinking about it. Of course, there is a relationship with their environment, and there is a little, they have discovered more, and their reflection is particularly strong. It is not stubborn on the one hand, they are always moving forward, to adjust themselves, so their divergent thinking and reflection ability is worth learning. However, the problem is, the sentence I have said, the status quo of the Chinese software industry, in 2006, the maturity, probably equivalent to the United States in 1986, a full 20 years of fall. Our start is from a farmer's country, a complete workshop, to change to the big industry, in line with the world software industry, there are many things to do. As someone drives now, the Chinese driving and the Americans are different. We are the most important, at this time, the education of the Software Academy should tend to regularize, tend to talk about Rules, tailorful things. This is not like the industry in the United States. The United States's industry has been in 1986, and the development of 20 years has passed a very painful period. It has been very complicated, very eloquent, and it can be said to be dogmatism. Therefore, people have developed from the DOD (US Department of Defense), like these things, or UP these things, sometimes they can fight in the United States, they have a rebellion, which is completely understandable. However, returning to our country's existing situation, I think we now seem to learn "Zhengshu" is still very important. As for now their tendencies, he also said, they are also exploring, he even, answer I that question, he thinks that the feelings they understand and some of our feelings are still different. They think they have been in these years, now they have been in the same year, he thinks they may use another way. So a lot of ideas are also changing. It seems that these two extreme things are good for us. We can learn from the middle school to some of their strengths, especially XP, such as Junit software, before you have Test before, this I see software The engineering industry has been recognized. I have already answered, what opinions can be discussed.
Martin: If my understanding is correct, I just mentioned that China needs to experience a process phase of the theoretical process, then in the agile process, like XP, because the United States has experienced such a process. I don't agree with this point of view, including this in the United States is also a process, many people have experienced such a process. I think in the United States, many projects need a lot of funds for surface work, when you carefully observe the facts, you will find it completely confused. What you see is that they have already conceived a performance, but in fact, it is completely different. Alistair cockburn has revealed this problem when he has been studying the method very early. He studied some methodology and interviewed some projects and asked their work. His approach is very smart, he found the project leaders and architects, how is the process of interrogation? Made a record. After that, he went to find those real analysts, developers, and inquiry the process. He compared these two aspects and found that the answer is not the same. Official story looks good, but the real story is completely different, it seems to be more confusing. Many companies have not taken this heavy-duty development process, and we don't do this. XP can help the project solve such disorderly issues, and he did not see that RUP has competitiveness, this is a competition in disorder. We hope that the company will be able to use the way, naturally, and make it develop forward. Although it is also chaotic when used at the beginning. These methods can be used in the United States, I want to be able to promote in China. So I don't think you need a heavy way, you can skip this step directly. The second point I want to say is that there is an unclear place for the UML and the unified process. This is two completely different things, but it is usually mixed together. The original intention of people invented UML is that when you use UML, you can avoid using those heavy methods. I am using the frequency of UML and ten years ago. There are also many many UMLs, especially for patterns. UML makes communication very convenient. Don't think you can perform complete analysis and design via UML, which is not the only use of UML. I painted UML map on the whiteboard, used to explain some problems in the book, UML is very important. UML has many ways to apply. In the agile process, UML has a very important role, of course it can also be used for heavy duty processes. But don't confuse these two concepts. UML is a very important tool with different applications.
