A skill is a skill. It needs practical, not to start with everyone. Conclusion Programming is an extremely important trick in XP, so it is worth cultivating this habit to use its benefits.
The architecture is reflected in the exploration, reflecting in metaphor, reflecting in the first iteration and other places.
XP processes the architecture by the following mechanisms: exploration, metaphor, first iterative, small version, reconstruction, team practice.
Metaphors provide a consensus and a set of public vocabulary. It helps to form a new understanding of problems and systems and help guide the structure of the system.
The Extreme Programming (XP) team is not completing all things in the final "one moment", but uses a series of iterations. The iterative interval is fixed for one to three weeks. Iteration is time limit: If the team can't do everything, they will give up certain features, not the deadline for delay iteration. At the end of each iteration, the customer can see the system that is ready to be published and the selected story is accepted.
As a customer of the Extreme Programming (XP) software, you will write test, answer questions, and definition priority with the team in all time. Customers and teams are an important influencing factors that help teams complete their work as soon as possible.
During the iterative period, customers have four main work: answer questions, write acceptance tests, run acceptance test, know iteration. And a preparation work in the version (after several iteration): Accept the version.
XP itself does not have analysts, customers work directly with the programmer. XP strives to achieve high efficiency mechanisms that make questions directly with people who may solve problems.
Several main tasks of the manager: deal with external groups, form teams, access resources, management teams, and deal with team issues.
Trackers will track three basic things: version plans, iterative plans and acceptance tests. You can easily track with simple spreadsheets.
The coach role in XP has developed into a "on the spot" helping team to maintain progress. Monitoring, implementation, and changing the process; guidance; providing toys;
XP is not a constant, it is also in the process of continuous development.
The above content is from the "Exploration Limit Programming" People's Posts Publishing House William C. Wake Zheng Ronglin Translation is the second part of the reading note (XP program)
