this is the subtitle of the book " Process Oriented Management "by Thilo and Uwe Knuppertz Feddern. At 293 pages, the two management consultants of the BPM & O describe in detail how process management is a holistic methodology can be established in an enterprise. Process management to understand the authors as a holistic management method. The book is not described as a single process is optimized. It deals with how a business process-oriented and align the goals can be achieved. The book addresses the middle and top management, which would be closely involved with the issue. (more ...)

ISO9001, ITIL, COBIT, eTOM, GeLi, GPKE, SOX, and many other frameworks have something in common:

Standardization of processes

But unfortunately all too often made to standardize a straitjacket. And with this straitjacket even simple activities an almost impossible task. Unnecessary and inflated forms, multiple release levels, through regional consolidation and monitoring delusions often lead to restrictions in the working lives of employees. What are the consequences? ... Creativity! But do not want to see the creativity of a company. The employees to be creative to bypass the laborious and expensive process standards attached. Even if the order is for a pencil of state, the employees have no other choice. Therefore, it is important to listen and put on a lively process management. This is a nice article on Spiegel.de to find even more examples in the book I'm working in a madhouse: From normal everyday office .

In the third part of my tip series on Business Process Management I would like to address a few key points about process modeling and process design. Since forming in any BPM project at least one process model, the foundation stone of the project is extremely important that the quality of process models is also fair.

(More ...)

In the second part of my tip series on Business Process Management I would like to address fundamental project management issues: strategy, goals, communication and risk management.

(More ...)

After the third workshop on agile BPM there are new questions for which we must find an answer. First, we have expanded our focus. We now consider not only scrum. We will now examine some aspects of agility on their applicability in BPM projects.

The thesis that the agile techniques, process models, principles and approaches to faith in BPM projects have an advantage gegnüber classical methods still stands. Above all, the point speed and flexibility, the "agility" while successfully implement BPM projects.

To check this hypothesis we have (friend of camunda Jacob, Christian Weiss of oose, Martin and I Bartonitz of Saperion Seven Principles) are based on the structures, the Christian in his video shows more engaged with the issue. Here we have once again found that the projects on BPM can be very very different. Even if we set ourselves a very simple IT-based process. Today's technologies are based on a still very intense programmed implementation (eg jBPM) to the zero-code "development" (eg Intalio or inubit). These differences are reflected in the consideration which naturally agile components can be put to good use again.

The interesting questions for me to date are:

• How do I deal with zero-coding iterations in BPMS?
• What should I look at the various iterations when interfaces are involved?
  • This interface and an enterprise service bus contracts make sense?
• Is there any sense in the BPM 2.0 prototyping approach apply?
• What do I need if I'm in my eighth iterations, a high degree of dependence on "external systems"? (Eg if one interface is also instructed to consume one wants, but to access, complete the bz only has limited influence)
• How can you break down projects make sense? If my process still needs to be developed as a GUI, then this GUI development is yet again a classic theme in the development of BPM project
• How to treat change requests in the BPM project? Especially if these CRs have a significant influence on the process.

In all these considerations, I find myself once again very close to IT projects. But it is always important to mention that IT's share is in BPM projects often only 20% of the overall project.