Agile Extreme Programming
What is Agile Extreme Programming
Extreme Programming (XP) is a high profile agile process.
Extreme Programming has defined practices and guidelines that implementers should follow. The process begins by gathering stories. Each story is business-oriented, testable, and estimable defined by the use cases.
Extreme Programming emphasizes teamwork. Managers, customers, and developers are all equal partners in a collaborative team. Extreme Programming implements a simple, yet effective environment enabling teams to become highly productive. The team self-organizes around the problem to solve it as efficiently as possible.
What are four basic values supporting XP
Communication – Without communications project schedules slip, quality suffers, and the customer’s wants and needs are misinterpreted or overlooked.
Feedback – The need to check our results is important. Without feedback, a project will most likely fail. Feedback tells how a project is doing while providing direction for future iterations.
Simplicity – Do not add unnecessary artifacts or activities to a project. Eliminate everything not completely justified.
Courage – Putting faith in the people over the process requires courage. It is important to realize, however, that if processes do become more important than the people do, a project is headed toward failure.
Respect - Trust your team members not to submit nonworking code
The ways XP Programming Works
Pair Programming - Teams of two people
Test Driven Development - Writing lots of tests, and writing them early
Continuous Integration - Putting code together as you write it, not at the last minute
Coding Standards - earn and follow well-established conventions
Collective Code Ownership - You are responsible for your partner’s code
Simple Design
Certification
Aptitude