Extreme Programming (XP) is an agile project management method and has many similarities with the Scrum method. XP is characterized - like all agile project management methods - by continuous iteration cycles. The requirements are recorded as user stories (as in Scrum), the effort is evaluated in story points (as in Scrum). However, while there's is only three roles in Scrum (Product Owner, Scrum Master, Scrum Team) XP knows (or defines) slightly more roles: Product Owner, Developer, Project Manager (leading the team), Customer and User (the latter two must not be identical).

XP attaches great importance to intensive communication with the customer. In order to avoid unnecessary complexity, XP focuses on early evaluation of the benefits of features (program functions) to ensure that only the really beneficial features are realized. During the implementation process, those user stories with a high benefit and a high risk are implemented at the beginning; in the second step, those user stories with high benefit and low risk are converted to BEginn.

In XP, test-driven development is often applied; tests are started very early to avoid risks and improve quality.


The author is a manager in the software industry with international expertise: Authorized officer at one of the large consulting firms - Responsible for setting up an IT development center at the Bangalore offshore location - Director M&A at a software company in Berlin.