All participants of the full team XP project (developers, business analysts, testers, etc.) work together in an open place, they are members of the same team. The walls of this place are randomly hanging on a large, significant chart, and some other things that show their progress. The planning game plan is continuous, step by step. Every 2 weeks, the developer will estimate the cost of the candidate characteristics in the next 2 weeks, while the customer selects the characteristics you want to achieve based on cost and business value. The customer test is part of the desired feature, and the customer defines the automatic acceptance test to indicate that the feature works. The simple design team maintains the design and the current system function item matches. It passes all the tests, does not contain any repetition, expressing all the writers want to express, and contain as little code as possible. Ending all product software is built from two programmers and placed on the same machine and placed on the same machine. Test-driven development programmers work with a very short cycle period, they first add a failure test and then pass. Improvement design improves bad code. Keep the code as clean and expressive. The continuous integration team is always integrated with the system. The collective code ownership can improve any code at any time at any time. All code in the code standard system seems to be a separate one ---- is very competent ---- people write. The metaphor team proposes a public scene of a program working principle. The sustainable speed team only has a wins hope. They work hard to work for a long time. They saved energy, they see the project as a marathon, not full speed short run.
