Extreme Programming (XP) - kirillsats/FirstAppBuketov GitHub Wiki

Extreme Programming (XP) is one of the agile methodologies. Despite the name, some practices have already become industry standards - such as refactoring and continuous integration. XP focuses on simplifying the development process, minimising documentation and maximising customer feedback.

XP helps you adapt to change, respond quickly to customer needs and deliver a high quality product. Here are the main problems XP can help with:

• Evolving requirements: XP uses short iterations and frequent releases, allowing the team to quickly adapt to new customer requirements.
• Code quality: Pair programming and continuous rewriting help maintain high code quality and early detection of errors.
• Team communication: Daily meetings improve communication between everyone involved in the project, facilitating rapid problem resolution.
• Time estimation and planning: “Release planning” and “Iteration planning” help to estimate the time needed to complete tasks more accurately and allocate resources more efficiently.
• Feedback and testing: Continuous testing and integration allows you to quickly identify and fix bugs, improve product quality and provide rapid feedback.

1. Simplicity - XP focuses on developing what is really needed, avoiding unnecessary complexity.
2. Communication - open and honest communication within the team is seen as critical to the success of the project.
3. Feedback - XP includes frequent and rapid feedback from customers, allowing the project to adapt quickly to market demands.
4. Courage - the team needs courage to make decisions, design changes and maintain high quality standards.
5. Respect - each team member is valued for his or her contribution, and everyone must respect the opinions and work of colleagues.

1. Planning - XP requires constant viability checks and adjustments to the work plan.
2. Management - In XP, it is important to maintain a balance in the work process by ensuring adequate information and task sharing.
3. Designing - starting with as simple a project as possible, which can then be made more complex.
4. Coding - coding should be done with the client and involves pair programming to improve the quality of the code.
5. Testing - all code should be unit tested before being included in the project, additional tests should be created if errors are found.

---

---

1. Collaborative planning. All project participants - clients, architects, developers - plan the work together to have a common understanding of the goals.

2. Client participation in test development. Clients help create test criteria so that the result meets their expectations.

3. Regular releases. The team frequently showcases the results of the work to get feedback quickly.

4. Simple and effective design. As clear and functional solutions as possible are chosen to simplify implementation and maintenance.

5. Pair programming. Programmers work in pairs, share experience and control code quality at once.

6. Test-driven development (TDD). First tests are written, then the code that should pass them.

7. Constant refactoring. The code is regularly improved: its readability is increased and complexity is reduced.

8. Collective code ownership. Any programmer can change any part of the project to improve the result.

9. Continuous integration. Changes are often merged into common code, which helps to find and fix bugs quickly.

10. Realistic workload estimation. The team takes on as many tasks as it can realistically accomplish without overloading.

11. Common communication language. All participants use the same terms to describe the project to avoid misunderstandings.

12. Adherence to code standards. All code is written to generally accepted quality and security standards.

In XP, planning and feedback help you adapt to change and continuously improve the product.

• Release Planning: Define long-term goals, core features, and release schedule with the customer.
• Iterative Planning: Selecting tasks to sprint into small manageable chunks.
• Daily meetings: Short stand-up's to synchronize activities and identify issues.

• From the customer: Ongoing customer involvement, regular feedback and course corrections.

• Testing: Tests are written before the code, which allows you to quickly identify bugs.

• Pair programming: Two developers write code together, reducing bugs and sharing experience.

• Retrospectives: Analyze past sprints to improve processes for the next one.

---

Role	Description
Customer	Defines requirements, sets priorities, and participates in acceptance testing.
Programmers	Write code, create tests, refactor, and implement changes. Everyone shares responsibility for the code.
Coach	Helps the team follow XP practices, provides mentoring and support.
Tracker	Monitors task progress and helps the team analyze actual velocity and planning accuracy.
Tester	Assists in creating automated tests and ensuring sufficient test coverage.

---