HEHE, this is not what I said. He told me when he listened to Larman yesterday.
Craig Larman, proposed GRASP mode and PV principles, and book Applying Uml and patterns (UML and Mode Applications, Chinese Edition is already out); Agile & Interestive Development-a Manager's Guide. The content of this lecture is mainly about iterative development and agile methods.
In the middle of questions, I asked the biggest doubts of XP when I developed products, how to increase customers' participation? Because our customers (in fact, it is very busy) very busy, it is not easy for a month, and each time is difficult to guarantee. I always think this is the biggest risk of the project, but I don't know how to solve it.
Don't use XP! This is what he answered my first sentence. Because of it, I don't have a live customer, so I can't implement this practice. Only all key practices are combined (at least there must be on-site customers, code public, pair programming, test driver, plan game, and continuous integration) can be called XP. Therefore, what we implement is not XP. Agile development methods do not only have XP, you can choose other methods for more process support for demand.
I heard such an answer, the first feeling is a bit unacceptable, the truth is true, what I first thought is that the larman is more "pro" RUP, so that the XP is to show the wider adaptability of agile UP. In fact, what he said, I also understand that Beck is clearly written in his own book, and I am very clear that the project is far from the standard of XP, just try XP.
However, my first feeling is still difficult to accept. Start, I think it is because I misunderstand that his suggestion is completely abandoned XP practice, such as TDD. But later, I understand that I am too loved to love XP, not a practice or because of its validity, but because of its conceptual unity and the human beliefs contained in the humanities. Although, I know that the team has not yet to XP, but I am eager to become an XP team in a certain future. Therefore, in the clear understanding of the limitations of the conditions, it is no longer able to adapt to the method of use, I still adhere to the unreasonable process, but just look forward to falling a live customer from the sky. Because I can't say that "dont't use XP", this is exactly the problem, I have overwhelmed the interest requirements for customers, the result is to apply a cool process to make software instead of In order to meet the needs of customers. It turned out that the mistakes made in the technical level have been made in the process level. I suddenly understood that "Agile Software Development" is a slight exaggeration "as a programmer, you must understand that XP is not your only choice."
Go back and talk about the lecture, Larman's lecture is very good, from the broadness of the content to the scene, very good (especially after taking TDD in the company today, the speech is really a trick that needs to be used.). It is a pity that it seems to be the reason for the propaganda of the Organizers (the source of IT), and the people will be quite small. The translation of the scene is like the reason for the cost of the provincial cost is the organizer of the organizer. It is not his English horizontal, and it is true that it is quite good. However, interpretation is also a skill that requires special training. The final result is that the whole translation is basically white.
At the beginning, the organizers specifically explained the reason for the cost, they were finally oblegation to Larman through repeated negotiations (of course, we are not free, they still need to spend a spending fee). But such an organization level, I think it will not promote better exchanges. This harvest is: the comparative system understands the theoretical history and key ways of iterative development; it is relatively wide to know the agile method nationality; there is a rough but more clear understanding of agile modeling. Unfortunately, it is a bit short day, and some aspects can be better.
Oh, yes, there is a big harvest to meet a beautiful MM on the car in Shanghai.
