The path of BPM for a software developer

I am Kobayashi, an ordinary software engineer, engaged in BPM (business process Management) software development work. I do not have a few decades of technical background, can not talk like Daniel, the way to judge the development of BPM, is not a senior process management experts, with you to analyze the ills of process management. I'm just a software developer with a round of work experience, and more accurately a process developer, with a few special experiences that can pry into a trace of the development trajectory of BPM development.

In 2004 , I first entered the software industry. At that time, most of the domestic BPM software products are still in the conceptual stage, they are basically very professional middleware-grade products, complex state machine, activities, events and other concepts flooded among them, only a high level of development and implementation personnel to control. Also, many users do not have enough knowledge of BPM to form a good BPM ecosystem, resulting in the inability of BPM products to function fully. Another product that contains workflows, OA (office automation software), is booming, and it's a great way to go. Through working relationships, while doing software projects for several large enterprises, I also have an in-depth understanding of their OA system, and have a strong interest in the form and principle of workflow in the system. This also opens up my path to BPM.

In 2007 , I took over two information management system projects, all of which have a piece of content that requires the collection, collation, replenishment, review and release of business data. I associate with the concept of workflow: A series of interconnected, automated business activities or tasks. Project when using workflow no doubt. However, the company does not have a workflow product or program, the project can not introduce external products, and finally can only imitate the previous understanding of the OA workflow self-practice. Build templates, define activities and sequences, code control process trends, set positions by parent activities Select subordinate activities specific participants ... A few months later, the so-called "workflow" platform was built up, and finally the user's approval. However, the project maintenance is difficult, the handover is difficult, the special application scenario process does not support, the process often appears the flow abnormal, cannot track the process and so on endless, let me miserable. A strong desire arises: I need a professional workflow product!

In 2010 , I was fortunate to be involved in a number of companies in the workflow product technology Exchange, to take note of the H3 BPM as the representative of the product, the BPM from the middleware to a "process rapid development platform", BPM is it's development tools, the process, forms and other general concepts as the center, Regular IT staff can get started. Next, working with H3 BPM, I've done a number of major projects that have been recognized by customers. Surprise, I fell into confusion, when BPM is the middleware, the biggest cost is the development cost, when the BPM transformation into a process development platform, the biggest cost is "demand communication costs." According to our project statistics, 80% of the cost of process implementation comes from demand communication and project management. If the process rapid development platform can also be transformed into an operations-level platform, then the cost of BPM construction will be greatly reduced. Especially for the need to constantly iterative optimization of the process management, more at any time to optimize management, the value of BPM will be further amplified, more enterprise-respected. How can we reduce development costs and become a problem for our process developers to think night and day.

Fortunately, in2016 , H3 launched 10.0 products to "the world No difficult process" as the goal, the BPM from the process of rapid development platform into operations-level products, ordinary IT administrators and even business personnel can be mastered. H3 BPM opened a new door for me, providing a easy-to-use, self-developed, and ubiquitous dual-engine, the overall cost of significantly reduced business process management products, so I can more efficient and faster to provide customers with process development services. It is more configurable than OA, does not require professional developers, ordinary enterprise IT managers and even business department personnel can play, more easily integrated than EAI, the enterprise management System unlimited connectivity, like Internet products as easy to use, so that users enjoy the ultimate experience, but also maintain the original BPM deep expansion capabilities, Depth analysis functions, and more. In the process development project, looking at the customer in the realization of the needs of the smiling face, I feel proud.

From the initial it rookie to the senior PM, from the process of small white to half process experts, I looked at the process management products from the initial business process management concept change to an increasingly open and powerful operation and maintenance level development tools. I'm growing, and BPM is changing, what about you?

The path of BPM for a software developer