Much of the discussion about collaborative methodologies like Lean, Agile and Design Build has, in the past been about creating continuous flow of value, team dynamics, technical practices and even the project management techniques required to get effective and acceptable products delivered and/or deployed. What teams in all environments quickly find out, however, is they are dependent on other organizational dynamics outside their purview, like securing customer involvement, issue escalation, resource allocation, even facility management becomes important.

BPMN 2.0 is almost here.  If all goes as planned, it will be voted on by OMG members in June. Assuming it passes, that doesn’t mean BPMN 2.0 is officially adopted and available in commercial tools, just that it has entered the “finalization” phase when tool vendors can start building it in. Even though the diagram notation of BPMN 2.0 appears little changed from previous versions, it represents a big step forward.

“A high level of process maturity is considered a fundamental pillar for comprehensive process automation and successful future implementation. The process operation and the time this process has been utilized by the business must be well understood by the person or people who are going to automate said process. Considering implementing a theoretical process or a process that possesses a low level of maturity is likely to result in failure and/or extended execution time and/or a high investment in cost and resources.