Provide the description of each phase of updated XP after introducing ETVX and explain how this pattern affected the XP lifecycle.

The entire development process consists of eight phases. The name of these phases are Exploration phase, planning phase, release planning, iteration phase, iteration to release phase, production phase, maintenance phase and death phase.
Exploration Phase: The exploration phase is the early XP life cycle that deals with model architecture and their requirements of the system. This part defined the requirements of the user, architecture, the tools and technology. 
Planning Phase: After the exploration phase, planning phase begins to strive for the answers to the two questions for real; what should be built within the time period with some business value and what will the plan do for the next iteration? In this phase, the task is derived from user stories and written on the task cards.
Release Planning: The most important goal of planning is learn about system and delivery of requirements plan of these functions. Exit or release planning consists of three phases: exploratory phase, commitment phase and steering phase.
 Iteration Planning:    Every iteration starts with its planning and schedule. At this stage, developers are preparing a plan for their tasks to implement the required functions of the current release. Programmer planning iteration chooses tasks to implement and appraisal the required costs and time and effort for the special task. Tasks can be specified to others programmer to equilibrium the assignment.
Iteration to Release Phase: This section includes major development tasks such as designing, coding, testing and collaboration. In this phase each repetition can take one to four weeks.
Repetition begins with planning. In the first repetition, such stories are chosen to make the general system architecture.
Productionizing Phase:   Because of a repetitive and incremental process, XP delivers software for small releases. This phase is about using the software in small releases. Its check the software is ready for production, acceptance tests, system tests and loading tests are performed. During this time, programmers slow down the level at which the system grows. Because risk has more important if a change is go to the next release or not.           
Maintenance Phase: It is a natural event for software systems. In XP, the software continues to grow over time. At this stage the new functionality is being built while maintaining the old one.
Death Phase:  This is the last phase of XP. There are two available settings where a software system has reached the death stage. In the first case, if the built-in software has all the required functionality and the customer is satisfied and no more stories, then it's time to finally run the system.

Affectedness of XP lifecycle:
            Extreme programming is a popular method for software development Agile. It has been specially designed to deliver the maximum amount of code within the shortest time. Extreme Programming developers are always placed within a stringent timeframe. Therefore, this method is the highest level of customer engagement in other Agile forms. ETVX affected the lifecycle of Extreme Programming. Updated XP life cycle after introducing ETVX (Entry criteria, Tasks, Verification & Validation, Exit criteria) used to development their process. During the verification check if an activity fails, the remedial actions are taken or a post-processing is ordered. It can be used in any development process. Every part of the process can be deliberated as an activity and described using the ETVX model.