The following is a little idea after I am participating in the application XP software engineering method project, welcome all the colleagues to discuss:
1. XP development methods are not suitable for a long period of development tasks. Time is long, due to lack of relevant documentation, the various management and control involved in the project will be confusing. For example, the synchronization relationship between the requirements and the version, the synchronization between the test scheme, and the demand, as well as the control, demand change and control of demand and design changes. Personally think that XP development is suitable for no more than two months of project cycles. Don't just use the name of XP, but actually a workshop development method.
2, courage XP requires "changing the courage". The courage is what, but more important is to see the consequences of changes. Changes were made with unnecessary courage, and the results were delayed, and the loss of time human resources was not sufficient to make up for the benefits of changes. Moreover, this "change" should refer to a change in demand. If during the development process, in the case of a stable demand, it is necessary to reflect on the system design idea within the group.
3, unnecessary debates in XP, pay attention to communication between the group people, but this communication also needs to be controlled. Since each member has its own design idea, the issue of the same purpose often has its own solution. In the debate, there will often be arguments between two or more paths that can achieve the same purpose. This is very common in software development. Usually this argument lasts for a long time due to the personality of the software personnel, and it is often finally not the discussion of the technology, and it becomes a fight against the mouth of the mouth. This argument needs to be controlled. Personally, a better way is to write your own point of view, listing its pros and deepening, and then make decisions and judgments by decision makers, or more experienced people.
4. Management roles are indispensable whether it is XP or other development methods. First, its function must match his role. Making management is also developing simultaneously, and the result can only be delayed, or to change other modules for the development of managers. Personally, the administrator of the project is actually a more smooth project, providing convenience to system analysts with customer exchange, to design and develop people with unrelated obstacles, provide the necessary conditions for technical support maintenance, supervision The progress, correction direction, meets the various needs in the project process. At the same time, the management role of the same project cannot be more, otherwise, it will fall into long debate and stagnation, and extreme situations may have the responsibility of each other.
5, a little supplement: the responsibility is clear
During the application of XP, it must strictly follow the complete property of each person's code. Moreover, the arrangement and allocation of the task must be implemented in a predetermined strict implementation. Prevent constant changes, so as not to cause unnecessary duties disputes.
Reply: I don't know why I can't reply to my document. So I wrote here. For Gigix's statement, I agree, but I would like to ask if you have no documentation, what method uses. XP is not a document, which is a lower priority. Document must have, for future maintenance, etc. I am actually hard to imagine software project management and maintenance of documents. Maybe there is a high person in this area?
