Teams using XP has the courage to speak the brutal truths, no matter how unpleasant it is. We will see throughout this article how many practices in XP exist because XP teams want to get as many and as frequent feedback as possible. Daily deployment to production is about feedback whether the code will really work in the real environment that will be used by the customer. Continuous integration is about getting quick feedback about whether the application is integrated. Pair programming and test first development are about getting live feedback about the code quality. Just like Scrum, XP values Courage and Respect. XP values are Communication, Simplicity, Feedback, Courage, and Respect.

Okay, one of the reasons why XP is not only about technical practices is because just like Scrum, XP is based on values. That means any Scrum elements that are not described here is because either XP does not have it or XP teams are doing it implicitly.

So in this blog, the perspective I will be using is from Scrum perspective. We'll see why XP is not only about technical practices in this blog. Just like Scrum, XP is also about mindset and behaviours. XP is not only about technical practices. You may also have heard on the street that 'XP is Scrum with technical practices'. Scrum teams who are religious in doing retrospectives will discover that they need to do XP practices if they want to go full steam in the future Sprints. My natural answer to this question is professional Scrum team will use XP practices. I would like to discuss Scrum and XP because I often get a question 'When should I use Scrum or XP?' from people in the community. Alrite, this time I am going to discuss Scrum and eXtreme Programming (XP). It's been a while since my last blog on 'Scrum And. Welcome back to Professional Scrum Developer (PSD) blog series with yours truly.

Extreme programming explained pdf