XP (eXtreme Programming) is better than Scrum, as XP defined DevOps 20 years ago

XP (eXtreme Programming) is well ahead of its time. However, few projects adopt it though XP is more correct and practical.

Today I picked up Kent Beck’s ‘Extreme Programming’ book (2nd ed) again from my bookshelf. What a great book! I have read it many times. Over the years, the XP (eXtreme Programming) practices make more sense to me.

Updated: 2022–05–27

XP started Agile, and the ‘Extreme Programming Explained’ book was published in October 1999. 22 years later, many projects branded themselves as ‘Scrum’ under ‘Agile’ while XP has been forgotten. Why?

First of all, the name matters. To an executive's ears, XP is probably not a good name.

• Extreme
  “I want to play safe, the fewer risks, the better”. This mindset explains the “Nobody Ever Got Fired For Buying IBM” proverb. (Fobes’s article “ ‘Nobody Gets Fired For Buying IBM’. But They Should ” is a good read)
• Programming
  “I manage programmers (and don’t know to program), not the other way around.”