I agree. Computer technology changes every 5 years and we are now expected to keep pace with the latest technologies on our own time, I think the same is expected with management skills. In a sense, these skills are easier to develop because the required skills aren't changing as fast.
With the computer skills, I have to learn the new technologies on my own if they aren't being used at work yet. With management/leadership skills (project planning, budgets, IP law...), they are obviously being used at every company and there are more chances to learn (insert bad management joke here).
Most good managers are overworked and there are opportunities for on the job training. Do some research, read some books, and then ask your boss to take one thing off of his plate. Start small and build from there. Note: A bad boss will be unwilling to give up responsibility for fear of you showing him up and taking his job. A good manager/leader will is interested in developing those under him and realizes that you doing a good job reflects well on both of you. A good manager doesn't have to worry about you taking his job. He should be moving up (not sideways) anyway.
Some good places to start training are:
1) Agile development: By definition, SCRUM masters come from the development team, not the business/management team. This is a good intro to management & leadership skills, and the Sprint Demos give you good opportunity to communicate with the business and management teams.
2) Scheduling: In a non agile environment, this means owning the Pert chart. In agile, it might mean helping prioritize the product backlog and contributing to ROM estimates.
3) Customer Satisfaction: Sometimes product maintenance (bug fixes) can involve lots of customer interaction. Making unhappy customers happy is a useful skill that will get you noticed.
4) IP Law: Reviewing existing patents for conflicts is a boring job. Sometimes the legal team creates a huge list of patents where half of them can be dismissed right off the bat. Maybe you can take a first pass at the patent review and just summarize your thoughts in an Excel spreadsheet with High/Medium/Low priorities so that other managers can focus on the high priority ones first. This will give you insight into the whole process and a foot in the door.
5) Interviewing: Any potential candidate should be reviewed by multiple people. Not just the boss. Again, read some books and do some research on good interviewing techniques first. Then see if you can participate in interviewing candidates. This area can be tricky because your interviewing style might conflict with your managers. He may not like your style, but that doesn't mean you are wrong. You will probably handle the interview differently depending on whether you are doing it with your boss or not. I suggest the 5 Why's style here. As a new interviewer, your opinion will matter less. If you use the 5 Why's then you will have much more detailed facts on why the candidate did what he did in a certain situation - your comments will be based less on your opinion and more about what you got the candidate to say. During the candidate review after the interview, someone may bring up a scenario that the candidate discussed and say he did the right thing. You will be able to go 3 levels deeper into the decision process used by the candidate to verify if this is actually true.
These are good places to start. I don't think you will get much finance/budget exposure or deal with any equal opportunity issues if you are not a manager. On the leadership side, there are always changes to exercise your skills as a mentor and leader without having the official title. This is just part of doing your job.