It's that, but it's also (perceived) pedigree. A lot of "business analysts" come from big consultancies like McKinsey, or investment banks like Goldman, et al. Managers and MBA-types have a mystical perception of those firms -- almost as if they trained jedi business knights. The truth may be far from it, at least in my experience. But perception usually trumps truth.
The best way to improve bargaining power is to be willing to walk away at a higher offer.
Another tip I heard, and tried out, is to start with a price higher than the highest you think they're willing to part with. Even if you cringe to say it. On the logic that the price can easily come down, but it's far harder for you to push it back up. (If they accept your first offer, the reasoning goes, you didn't go nearly high enough. Remember, that first price can affect you for years.) It worked for me, though of course YMMV.
(For those who cringe in salary negotiations, Graeber's _Debt: The First 500 Years_ may give you some perspective on why it makes you feel bad.)
Definitely helps to get in a position where you interview people. (Not to mention salary negotiations.) Then it'll be clear what employers want, and what other developers do. Based on that, you can present what they truly desire.
Take for example do-at-home projects. If you can solve them, then you can really hit them out of the ballpark. The first time I reviewed the solutions, I saw that only one or two had neat complete-ish solutions. (Most had significant cut corners; one was written by an insane fellow.) It was easy to see how to go beyond the best ones: make a build file, a readme that's worthy of a good opensource project, etc.
I like this point a lot, and it makes sense, but then I thought, how come it doesn't apply to athletes ?
The classical worker, the kind I believe the GP meant to refer to, is a commodity. It's the kind of workers it might make sense to hire as day labourers and, conversely, for whom collective bargaining is beneficial.
There has been a tendency for some businesses to treat programmers as this kind of workers, often leading to failed off-shoring efforts.
If you're great at operational work, but are no good with tactics or strategy, you won't ever get a huge salary, in the office or in sports.
After all, look at pro-sports salaries and you'll see that the highest paid players are the ones who are put in situations where they have the ability to make potentially critical decisions, and who have a history of being relatively good with those calls.
Read up on the Reserve clause and Curt Flood for more info about how this all changed starting with Major League Baseball in the 1970s.
(Maybe it helps to read _Getting to Yes_, or something.)
Plus, there's an obvious class component. The further removed you are from working with your hands, the higher value you're perceived to have.
(After all, who hires these project managers and business analysts? Managers. Who naturally value themselves more than underlings, and will transfer that value perception to these managers/analysts. This argument was used in Schmidt's _Disciplined Minds_ to explain some of the higher rank theoretical physicists have over experimental physicists and engineers, even if engineers earn more money.)