This morning, while waiting for the Office 2007 update, I was reading an article on the future of BPM - BPM in Ten Years? My Best Shot.
The combination of Scrum being implemented at work and BPM as my future professional target resulted in the idea that BPM's next incarnation will be a mixture of Scrum principles and BPM methodology.
To put it in a few more words, using Scrum, the team members are given freedom to choose their own paths to the target presented by the product owner. They act as rational personas and the result is a much more motivated and capable team.
On the other hand, currently there is little flexibility in the implementation of the BPM modelled processes. Very often the improvements are done like little "waterfall" development stages. There is little flexibility and continuation of the improvements.
This is exactly where the Scrum principles can help. They can empower the team members to provide feedback, influence the workflow and continuously improve, improve, improve... But then comes the question of the most proper management style to allow this to happen.
