I have frequent experience with a very long projects on Business Process Management made. Mainly through the cooperation of many departments in an end-to-end process is a process increasingly larger and more heavily-overdue project. Although many activities in the process often been fully clarified and may have even been developed already completed the process can not be imported because somewhere a little more activity will be coordinated. With an agile approach would allow all activities to be implemented more quickly and clear the desired result could be adjusted more quickly. Therefore, the issue of Scrum is very interesting, but not easy. Scrum was originally designed for software development and not for BPM projects. My first thoughts on this combination, I have already described in the blog (see Part 1 and Part 2 ). The same ideas have also Dr. Martin Bartonitz of Saperion and friend Jacob made ​​from camunda. For us to discuss and share the combination BPM Scrum and we held a small workshop with James in Berlin. The results of our first workshops are on bpm guide.de and looked up in the forum of the BPM network are discussed. I'm looking forward to the feedback in the forum.