What is Extreme Programming (XP)?

What does XP stand for?

Extreme Programming (XP) is an excessive, disciplined and Agile Software Development Methodology that specialize in Coding inside every Software Program development life cycle (SDLC) stage. These stages are:

Continuous Integration to find out and restore troubles early in the development manner Customer involvement and fast Comments

These XP method disciplines are derived from the subsequent 4 key values of Kent Beck, XP’s originator:

Communication: Communication between team participants and Clients have to occur on a frequent foundation and bring about open undertaking dialogue with out fear of reprisal. Simplicity: This involves the use of the simplest design, generation, Algorithms and strategies to meet the purchaser’s needs for the Modern-day venture new release. Feedback: Feedback have to be received at a couple of, distinct Ranges, e.G., uNit checks, Code evaLuation and integration. Courage: Implement hard but required choices.

What Does Extreme Programming Mean?

In addition to the important thing values, XP method Implementation additionally calls for the support of the 3 principles of incremental alternate, embracing cHange and high-quality work.

Twelve key practices also must be followed:

Some traditional technique practitioners criticize XP as an “unreal” method causing reckless coding. Several conventional Software Developers find XP inflexible with low Functionality and little innovative capability. Additional criticisms are that XP:

Has no shape. Lacks vital documentation. Has no clean deliverables, i.E., realistic estimates are hard due to the fact the complete challenge requirement scope isn't always fully described. (This lack of special necessities Makes XP noticeably liable to Scope Creep.) Needs cultural change for adoption. (May work for senior developers best) Is highly-priced, i.E., calls for frequent communication/meeting at the consumer’s expense, which may additionally lead to hard negotiations. Has possible inefficiency from frequent code changes within various Iterations. Of course, as with every improvement method, all this is very subjective and dependant on Personal choices.