BPM: Good or Bad for IT

I have heard people make different arguments about the future of IT and the role that BPM plays in that future.  It is an interesting argument.  Here are a few thoughts.

1. BPM is not necessarily technology dependent.  But, technology is often part of the solution.
2. BPM technology is not IT independent.  Don't believe the no code arguement that business can set-up and implement a BPMS solution without IT.  You need help with software installation, servers, maintenance, integrations, customization, and other traditional frameworks (e.g., change management) from your IT staff.
3. IT already has lots of problems.  If anything, a BPM solution can help IT.  It provides a common language for bringing IT and business together - process.  It provides a quicker way to deploy applications.  It allows for more agility in making application changes.  It provides a way for managing SLAs.  It gives metrics and reduces the adhoc query requests.
4. IT is already facing a staffing shortage.  I have heard a quote of 1.6% unemployment in IT thrown around.  Anything that helps deliver more with less is important.
5. BPM does reduce the need for IT involvement in every change.  It makes major rollouts less likely.  The projects become smaller.  Business people can do a lot more. 

So...I guess my opinion is that BPM is good for IT.  It increases their throughput.  It makes the success of their projects more likely.  It allows them to be more in synch with the business.  And, it closes the traditional business and IT disconnect.