Extreme development and agile development

has been in contact with extreme development and agile development, but it's a little awkward to say what they mean and how to describe it. So just calm down and tidy up well. Introduction

In 2001, to address the growing process of software teams in many companies, a group of industry experts summed up some of the values and principles that enable software development teams to work quickly and respond to change, calling themselves agile alliances. The agile development process is a lot of methods, mainly: scrum,crystal, feature-driven software development (Feature driven development, referred to as FDD), Adaptive Software Development (Adaptive software development, ASD), as well as the most important extreme programming (EXtreme Programming, abbreviated XP). Extreme Programming (XP) was first advocated by Kent Beck, a master figure in the Smalltalk community in 1998. Extreme Programming

    Design and programming are people's activities. Forgetting this, you will lose everything.      

                                                             --Bjarne Stroustrup   

Extreme Programming (XP) is one of the most famous agile methods. It is made up of a series of simple but interdependent practices . These practices combine to form a whole that is better than a partial combination. Agile Development

  The interaction between people is complex, and its effect is never expected, but it is the most important aspect of the work.

                                                            --Tom Demacro and Timothy Lister

    Agile Software Development Manifesto:

    Individuals and interactions outperform     processes and tools
    to work with software that is more than exhaustive documentation
    customer collaboration       Contract negotiation
    responds to change       better than follow plan

Keep the design as clean and simple as possible, and use many unit tests and acceptance tests as support. This preserves the flexibility and ease of understanding of the design. The team leverages this flexibility to continually improve the design so that the systems that are generated at the end of each iteration have the design that best fits the needs of that iteration.

This is just about understanding the relationship, the specific need to achieve their own.