Agile principles generalize to all software development. The specific application of those principles at one company won’t. That’s the core difference people m

Agile principles generalize to all software development. The specific application of those principles at one company won’t. That’s the core difference people miss. Of course then there is the difference between “software development” and “one individual programmer”. Not all programmers will gel with Agile stuff as well as the next one. That’s why it’s not supposed to be rigid (it often is when done poorly). But yes, an understanding of the principles is required to translate them into practices for a team. Rigid adherence to Scrum or XP is missing the point. For a good look at a way one company took the principles of Agile and applied them in a very effective but utterly idiosyncratic way... look at Spotify. Pt 1: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ https://labs.spotify.com/2014/03/27/spotify-engineering-cult... Pt 2: https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/ https://labs.spotify.com/2014/09/20/spotify-engineering-cult...