Word Salad on Extreme Programming

I'm trying to organize some thoughts on this. I don't expect this to make sense.

Project leaders are usually senior members of teams (in waterfall methodologies).

There is a project management skill that requires people to be fairly experienced in their positions before they're really good at it.

A lot of the stuff that is easy to point to and say, "This. This is what project leaders do" seems kinda... low skill level: tracking tasks; determining plan versus actual expenditures; gantt charting. Heck, there are tools that do most of this work. What seems to require experience is getting the project leader into a headspace where they think about things in project management ways.

The project manager is usually in conflict with the development team because they're thinking about things in project management ways, and the team is thinking about things in development terms ("let me bang out this righteous code...")

The headspace of project management is a shibboleth. It divides.

Extreme Programming is usually sold on its quality and "develop faster" benefits. I like its project management benefits. It simplifies the language of project management and turns it into something that a team takes ownership of, rather than something that the project manager takes ownership of.