What are the Extreme Programming (XP) Values?
The practice of XP is supported by 5 underlying values. This health check gets your team to indicate their current level of happiness across these values, along with any other key values that your teams aspired to.
The importance of knowledge transfers between team members through appropriate and frequent communication mechanisms.
Avoiding waste and to only do what is absolutely necessary to keep the system as simple as possible to create and support. It focuses on the requirements you know about, rather than trying to predict the future.
Getting and acting on feedback on designs and builds so that areas of improvements can be identified and adjustments made.
The courage to raise issues that are impactive effectiveness, to stop doing things that are not working and the courage to accept and act of feedback, even if it is difficult to accept.
Team members respect each other especially since they are working so closely together in an interconnected way.
How do these values apply to Extreme Programming?
Extreme Programming (XP) is the most specific agile framework for engineering practices that aims to produce higher quality software and quality of life for the development team.
It is most common for dynamically changing software, with small co-located teams supported with automated testing, and where there are risks caused by fixed time projects using new technology.
Teams sit together in a well set up workspace that lets people have focussed and energised work and paired programming (where 2 people sit at the same machine to allow for continuous code review and more rapid problem solving).
Customers, trackers, developers and coaches all work an in interconnected way to deploy and test stories on a weekly and quarterly basis. The 10-min build, continuous integration, incremental design and test-first programming practices also come into play.
Given this, team values remain crucial for this type of close knit practice. Take a weekly feedback session for example. Designs should be simple and effectively communicated. There needs to be good communication between the team and the users so that feedback is provided in a respectful way. The team then needs the courage to receive an implement those changes. The embedding of these values apply just as much to daily work practices as they do the quarterly cycle reviews.