View source for Old OCEB2F 03 Business Process Management Concepts and Fundamentals

[[Category:Private]]
[[Category:OCEB2]]

==Business Process Management Concepts and Fundamentals⌘==
===Fundamentals of Business Process Management⌘===
'''Source of information:'''

Bruce Silver, The BPMS Value Proposition, January 2007
* http://www.softwareag.com/jp/Images/The%20BPMS%20Value%20Proposition%20WP%20Final_tcm87-33844.pdf

Daniel J. Madison, Becoming A Process-Focused Organization, BPM Institute, 2007
* http://www.bpminstitute.org/articles/article/article/becoming-a-process-focused-organization.html

===Fundamentals of Business Process Management⌘===

[[File:BPMTheThirdWaveCover.jpg|100px]] Howard Smith & Peter Fingar, Business Process Management: The Third Wave, Fourth Anniversary Edition, Meghan-Kiffer, 2007 [ ISBN-10: 0929652347 ]

<!-- [[File:BPMaRigorousApproachCover.jpg|100px]] Martyn Ould - Meghan-Kiffer, Business Process Management: A Rigorous Approach, 2005 [ ISBN-10: 0929652274 ] -->
[[File:BPMSChangCover.jpg|120px]] James F. Chang, Business Process Management Systems: Strategy and Implementation, 2005 [ ISBN-10: 084932310X ]

[[File:FundamentalsOfBPMCover.jpg|100px]] Marlon Dumas, Fundamentals of Business Process Management, Springer, 2013 [ISBN-10: 3642331424 | ISBN-13: 978-3642331428]

====Different Organizational Approaches⌘====
<table border="1" cellpadding="10" cellspacing="0">
		<tr bgcolor="#BDBDBD">
			<td style="width:100px">
			<p>'''Methodology'''</p>
			</td>
			<td style="width:150px">
			<p>'''Level of change'''</p>
			</td>
		</tr>
		<tr bgcolor="#F2E0F7">
			<td>
			<p>Radical BPR</p>
			</td>
			<td>
			<p>Radical</p>
			</td>
		</tr>
		<tr bgcolor="#A9E2F3">
			<td>
			<p>Revision BPR</p>
			</td>
			<td>
			<p>Small Leap</p>
			</td>
		</tr>
		<tr bgcolor="#F2E0F7">
			<td>
			<p>TQM</p>
			</td>
			<td>
			<p>Incremental</p>
			</td>
		</tr>
		<tr bgcolor="#A9E2F3">
			<td>
			<p>Six Sigma</p>
			</td>
			<td>
			<p>Incremental</p>
			</td>
		</tr>
</table>

====TQM Principles⌘====

* Focus on work process
** Quality problems are mostly dependent on the work processes that designed and manufactured the products and services
* Analysis of variability
** Uncontrolled variances are the primary causes of quality problems, and these variances should be analyzed and controlled by the front-line workers
* Management by fact
** Quality improvements programs should be based on systematic data collection, analysis and experimentation for solution implementation
* Learning and continuous improvement
** Quality improvement is never-ending and employee learning is a major part for carrying out quality improvements

====William Edwards Deming⌘====
[[File:WilliamEdwardsDeming.png|200px]]
* The father of TQM
* 1900 – 1993
* an American statistician, professor, author, lecturer, and consultant
* National hero in Japan
* Unknown it the US until 1970s

====BPM and TQM⌘====

* BPM is similar to TQM in the way:
** Use of statistical data
** [[File:kaizen.png|100px]] Kaizen (continues improvement)
** Evolution rather than revolution
* Differences:
** BPM “requires” computers

====BPR Principles⌘====
Business Process Re-engineering (BPR)
* Management philosophy to enhance corporate competitiveness
* Tom Davenport and James R. Short – they prescribe a five-step methodology for achieving process redesign
* M. Hammer – he believed corporation were simply automating processes design prior to the wide usage of computers
* '''The key enabler for BPR is IT'''
* IT serves as the disruptive technology that allows generalists to do the work traditionally performed by specialists, enables everyone to make decisions

====Michael Hammer⌘====
[[File:MichaelHammer.png|200px]]
* Michael Martin Hammer (1948 - 2008)
* an American engineer
* management author (has he ever managed something?)
* professor of computer science at the Massachusetts Institute of Technology (MIT)
* known as one of the founders of the management theory of Business process reengineering (BPR)

====Lean⌘====

* Lean manufacturing
* Lean IT
* Lean software development
* Lean Services
* Lean Integration
* Relation to Agile (lack of documentation)

=====Lean Principles⌘=====

* '''Eliminate waste'''
** unnecessary code and functionality
** delay in the software development process
** unclear requirements
** bureaucracy
** slow internal communication

=====Lean Principles⌘=====

* '''Amplify learning''' - running tests as soon as the code is written,  increasing feedback via short feedback sessions during both customer representatives and the development team learn more about the domain problem and figure out possible solutions for further development
* '''Decide as late as possible''' - delaying decisions as much as possible until they can be made based on facts and not on uncertain assumptions
* '''Deliver as fast as possible''' - the sooner the end product is delivered without major defects, the sooner feedback can be received, and incorporated into the next iteration. 
* '''Empower the team''' - "find good people and let them do their own job"
* '''Build integrity in''' - the customer needs to have an overall experience of the System
* '''See the whole''' - software systems are not simply the sum of their parts, but also the product of their interactions

"Think big, act small, fail fast; learn rapidly"

===Becoming Process Driven Organization⌘===

* Process management is comprised of end-to-end documentation, improvement (from radical to continuous), and management of organizational processes
* Decisions are data-driven and based on customer satisfaction metrics, quality, time-lines, and cost
* The responsibility of monitoring process performance and facilitating process changes belongs to a process advisor or manager
* Administering processes is dramatically enabled by business process management technology
* Finally a process structure and governance is created to “cement” the move to process based management
More: http://www.bpminstitute.org/resources/articles/becoming-process-focused-organization

====Becoming Process Driven⌘====

* Process redesign efforts in one area precipitate change in others
* Changes are required for a particular process improvement to be implemented
<!--
* Sometimes, process improvement and redesign might propel an organization into full-scale changes such as moving toward a process based management organization
-->

====Becoming Process Driven⌘====

To completely align around process, firms consider the following areas:

* '''Interpersonal''': department heads evolve into leaders of links in a chain to create and deliver value
* '''Conceptual''': supervisors and managers shift from fire-fighting to structured, team-based problem solving using process improvement tools
* '''Cultural''': organization’s values must shift from individual recognition to process excellence
* '''Structural''': formal governing body that oversees enterprise processes, allocates resources, prioritizes initiatives, and links process to strategy is needed
* '''Technology''': software should be used to model, test, and improve processes

<!--
=====Interpersonal Changes⌘=====

* Uninterested and unhelpful department heads evolve into leaders of links in a chain to create and deliver value
* Do department heads and process owners respect each other? Is there enough mutual regard that they consider actions' effects on each other without being prompted by policy or structure?
* Is there an informal network of relationships that complements rather than undermines the formal matrix structure?

=====Conceptual Change⌘=====
* Supervisors and managers shift from fire-fighting to structured, team-based problem solving using process improvement tools
* Data capture and reporting must move from individual departmental performance to process performance highlighting critical customer requirements
* Beliefs and assumptions regarding the root causes of problems must focus on processes rather than people
* Processes methodologies such as Lean, Six Sigma, reengineering, process improvement and design principles should be used throughout the organization.

=====Conceptual Change (continued)⌘=====

Do the organization's senior executives:
* think with processes? That is, do they translate plans into process performance requirements rather than functional assignments?
* Do they view process capability as a strategic asset that must be cultivated and leveraged?
* Do they balance the company's vertical function organization with a horizontal process structure?
* Do they allocate resources according to process requirements?
* Is there a widely shared understanding of process management that draws attention to the horizontal flow of work rather than to vertical hierarchies of control and communication?
* Can people use process terminology in everyday work encounters without having to provide a dictionary?

=====Cultural Change⌘=====

* The organization's values must shift from individual recognition to process excellence
* Pictures, graphs and stories should highlight process improvement successes
* Are there strong values about coordination within and across process teams?
* Are there strong norms against building fiefdoms or erecting boundaries?
* Are the organization’s cultural heroes are those who follow process solutions rather than rebels or cowboys who do without a process focus?
* Are errors viewed as opportunities to improve processes rather than evidence of personal failure?

=====Structural Changes⌘=====

* '''A formal governing body that oversees enterprise processes, allocates resources, prioritizes initiatives, and links process to strategy is needed.'''
* A process advisor or owner is added to the process team
* Managers and supervisors who are no longer required to make many of the decisions they used to must switch roles to become facilitators and coaches
* A formal, seniority-type reward system must change to one based on knowledge and results. Individual rewards should be replaced by team- and process-based ones.
* Changes in job descriptions should enhance multi-skilled and cross-functional capabilities (i.e., generalists versus. specialists). Also, the structure must accommodate the compensation for skill and knowledge
* Changes in traditional career paths should include more horizontal career moves rather than corporate ladder climbing

=====Process Driven Technology⌘=====

* Software should be used to model, test and improve processes
* Is the organization's information infrastructure designed to make process information available to all?
-->
=====Change Sponsor⌘=====
*Change (structural, interpersonal, conceptual and technology) requires sponsors
*A sponsor is:
**Person who has the authority and provides the long-term commitment, funding, resources and direction for an effort
**Executive manager of the unit that is undergoing the change
**Sponsorship should cascade down through the middle managers and unit managers that will ensure continuity of efforts

===Stakeholders' Roles and Responsibilities⌘===
====BPMM: Unit, Work Unit and Project⌘====

* A "unit" is an organization entity, headed by a managers. On an organization chart or organogram, the boxes (or other elements, including subordinate boxes) typically represents a unit. 
* The term "unit" is a recursive term and applies to every management level in the organization

====Organogram⌘====
[[File:organogram.png|800px]]

====BPMM: Work Unit⌘====

* '''Work Units''' are the lowest level units in the organization where the people who do the work can appropriately participate in the planning and commitment activities and where the manager is aware of work requirements and commitments and able to take corrective action
* '''A work unit''' is the level at which negotiations and commitments are made on requirements and budget. 
* Within a work unit, adjustments can be made as how the requirements, budget and commitments are satisfied, but they cannot be changed at that level
* Sometimes the work unit may be at the second or third level from the bottom of the chart

====Process Owner⌘====

* Responsible for the '''performance''' of the process
* Responsible for '''influencing functional workers''' and functional heads on how best to perform functions
* Should be a senior member of the organization
<!-- 
* Ensures Top-down commitment, Bottom-up execution
* Align employee rewards to process performance

====5 gatekeepers to success⌘====

5 gatekeepers to success:

* Stakeholder analysis
* Understand magnitude of change
* The organization's capacity to change
* Organization's acceptance of BPM
* Technical review


Source* Jeston and Nellis* Business Process Management
-->
<!--
====Diagnosing Processes⌘====

* Stakeholders are persons who care about and exert influence over the company, its processes, and its products. 
* Value chains and processes have stakeholders
* Since the customers of processes are usually the major stakeholders, assume that goal of a process is to satisfy the customers
* Other obvious stakeholders include:
** Owners (shareholders), employees, managers, partners, suppliers, government, public, competitors
* '''To see when a process is functioning correctly, develop a list of stakeholders and check what each one expects and how the process would need to be changed to satisfy that stakeholder'''
-->

===Enabling Tools of Process Management⌘===
====Technology for Executing Processes⌘====
[[File:BPMSSilver.png |800px]]

<small>Bruce Silver Associates 2007</small>

====Technology for Executing Processes⌘====

* The '''BPM Suite (BPMS)''':
** automates the human workflow (ability to create human tasks without code)
** continuously monitor process state and performance without code
** '''integrates data between backend systems '''
** executes the business rules, controlled by the process model

====BPMS compared to other IT systems⌘====
*The purpose of a BPMS is to coordinate an automated business process in such a way that '''all work is done at the right time by the right resource'''.
* Customer Relationship Management(CRM) systems and Enterprise Resource Planning (ERP) are process focused.
* '''BPMS exploits an explicit description of a business process, in the form of a process model''', to coordinate that process. 
* BPMS can be tailored to specific processes of any kind.
* BPMS is similar to a Database Management System (DBMS).
* BPMS can fully automate processes - '''Straight-Through-Processing'''.

====BPMS Overview⌘====
[[File:BPMSOverview.png]] 

<small>From: docs.jboss.org</small>

====Architecture of BPMS⌘====
[[File:BPMS_Dumas.png |700px ]]

<small>Fundamentals of Business Process Management, Marlon Dumas</small>

====Architecture of BPMS⌘====

* A process model can be deployed to the engine in order to be executed.
* Execution engine can:
** create executable process instances
** distribute work to process participants
** automatically retrieve and store execution data
* A worklist handler is the component through which process participants are offered work items.
* External services are applications (services) outside the BPMS that can be called by execution engine.

====BPM and SOA (Service Oriented Architecture)⌘====
* BPM without services is:
** Complex and brittle, because the process layer is required to access the underlying business applications directly
* The SOA provides the ideal platform for the business process layer for the following reasons:
** A line of business services provides business functionality that map the business tasks in a business process
** Business '''process is not responsible for knowing any details of the underlying application and technology platforms, '''because Service contracts for the line of business services provide well-defined and unambiguous interfaces for accessing the services

====Modeling Processes⌘====

Critical Needs in Tooling
* To make the discovery methodology work effectively, proper tools are required. Here we highlight two critical capabilities that the tooling should provide
* '''Validation'''
** In process discovery we have been discussing, there is the underlying problem of accuracy: How do you know the information you have discovered is consistent and complete? This is especially problematic in the distributed approach to discovery
* '''Integration'''
** Integration fitting process fragments into a coherent whole. This is especially true in the bottom up style of process discovery.
** The tool must understand the connections of the process fragments and then integrate the fragments into a coherent process that can be analyzed
====Questions⌘====
* Who is the father of TQM?
* What principles does TQM have?
* What is BPMS? Describe BPMS architecture.
* What is worklist handler?