Today’s challenge to increase productivity with fewer resources has lead to numerous methodologies and toolkits to help organizations meet their objectives and become more profitable and effective. This certainly makes the case for applying two well known and proven methodologies Business Process Management (BPM) and Six Sigma.
Resource Oriented Architecture
According to a 2008 Gartner Survey1 there has been an increase in the number of organizations implementing web services using Representational State Transfer (REST) and Plain Old XML (POX).
Reviews: Necessary Evil or Symptom?
During any BPMS demo, the vendor will demonstrate how the application handles the review and approval cycle of some work product, e.g., a document, form, or report. Review and approval of these products is a process cycle that all businesses share, and in my opinion, one that’s entirely too common. Reviews aren’t disappearing anytime soon. They are in some cases a necessary evil. However, let’s be clear – reviews aren’t value added activities.
Collaboration and Business Decision Management
Business Rule Management Systems (BRMS) have been described as the ultimate platform to achieve true collaboration. By bridging the gap between business and technology, two previously disparate groups that did not speak the same language could now do so in the universal language of business rules. And to a certain extent these systems met that goal. However, there have been persistent nagging issues centered around things like requirements and change management that seem to keep getting in the way of collaboration and, ultimately, true agility.
Process Management Scenarios and their Technology Requirements
One of the interesting BPM debates I’ve been following in the past months has been about the relevance of BPM technology standards such as BPMN and BPEL (with some protagonists claiming that BPEL isn’t powerful enough as a modelling or implementation language to express the richness of some processes; and others claiming that in fact it’s just fine – for example, see the online debate between Keith Swenson and Ismael Ghalimi.
BPM and Software as a Service
Today’s economic pressures are resulting in an increasing scrutiny on IT budgets and how to achieve the best return on investment. IT project portfolios are constantly evaluated by the CIOs in light of new budgets and constraints. Clearly IT spending is on the fall, significant budgets cuts are on way, and new initiatives are impacted. BPM initiatives that had initially made their way into the portfolio are now being re-evaluated given the upfront capital cost of procuring Hardware and software.
Fly-by-BusinessDrivers – Agile Supply Chain Organization with Business Drivers Embedded BPM System
As much as business drivers cannot be divorced from an effective and successful supply chain, the same is true for Business Process Management (BPM) that could help raise the bar for supply chain.
Supply chain in Organizations are very complex with numerous distribution types and channels, in house and outsourced factories, third party warehouses, logistics and suppliers with varied contracts, etc. Enterprise Resource Planning (ERP) software enabling supply chains greatly increase the availability of current information.
Integrated Business Management in the Process Age: Creating an Agile Business Management Paradigm
In the transition from the Information Age to the Process Age, we need new thinking and methods to design products and services for the agile business environment. Processes demand a new paradigm that expects more from managing a business and creating solutions than the current information-oriented paradigm. We need methods that are fit for working with processes to replace our methods for working with information, as they aren’t built on the necessary concepts.
Service Oriented Architecture – A Service Contract Design Template
Introduction
Service-Oriented Architecture (SOA) is a highly collaborative paradigm, and attempts to break down the invisible barriers between IT and business. A critical step to be undertaken when implementing a SOA is to identify, specify, catalog and document candidate services. Given the sheer complexity of the task, this is more of an art, rather than a science. However, there do exist some common-sense principles and best practices for this purpose.
Technology Does Not Matter, Methodology Does
Does it still matter what matters in Enterprise IT? Even before the current harsh times the field seemed to be a land of confusions and illusions, from CIOs greatly overestimating their departments’ and their own role in the eyes of their CEOs1, to business analysts continuously unable to get exactly what they need when they need it from their IT counterparts. And to a respectful analytical firm putting as much confusion as possible in one sentence: “Although the word ‘SOA’ is dead, the requirement for service-oriented architecture is stronger than ever” (sic!).