Phases of EXteme Programming

Phases of EXteme Programming

Planning: In this, the team of researchers proposed the idea of keeping the user's interest in mind. The team then set a series of targets to reach the end goal. If the team fails to incorporate every story of the users then spikes are used which indicate the need for further research.

User stories are used to express the requirements of the users.

Designing: The main aim of designing a customized plan is to minimize errors to the max. If the plan's design is up to par, the result will be evident. It involves the participation of the whole team when they gather in one place to discuss the future of the product.

Coding: In this phase, coding is done to generate a code, which fills all the requirements of the eXtreme programming. While developing a code, Practices of eXtreme programming are used to lay the foundation.

If the initial coding is done, the members of the team pass their review on it to fix any kind of bugs.

Following factors need to be in check when coding

  • The first thing to consider is to opt for a specific paradigm for the system.
  • eXtereme Programming gives Pair programming the most value. It involves the culture of working in pairs to generate a code.
  • It is a requirement in the coding to integrate a single pair of codes after every interval.

Testing: In this, the product is subjected to two types of testing.

In-house testing of the product is included automated testing to assure its functionality. In this, the whole team gathers to test the different features of the product and document their perspectives.

According to the feedback further action happens.

Acceptance testing is based on consumer input and their appreciation for the product. It incorporates the user's interaction with the product before launching it in the market. Members of the team listen to user's feedback and document their views