Top Banner
BPM and Scrum Chiang Mai 26. Feb. 2015 Dr. Karl Schindler, Antwebsystems Bangkok, 22.07.2015
29
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: BPM and Scrum

BPM and Scrum

Chiang Mai26. Feb. 2015

Dr. Karl Schindler, AntwebsystemsBangkok, 22.07.2015

Page 2: BPM and Scrum

Agenda

■ What is a Process

■ What Is BPM

■ Why BPM

■ BPM and Application Development

■ BPM and ERP

■ Traditional BPM

■ Agile BPM as Software Engineering Discipline

■ BPM and OfBiz at Antwebsystems

■ Q&A

Page 3: BPM and Scrum

Process Definition in BPM

■ A process is a repeated action with well defined start and end.

■ A process is not a continuously ongoing business function (e.g. Manage personal accounts)

Page 4: BPM and Scrum

4

What is BPM

■ BPM is a set of processes that help organizations optimize their business performance. It is a framework for organizing, automating and analyzing business methodologies, metrics, processes and systems that drive business performance. [Wikipedia]

■ “Business Process Management (BPM) is a disciplined approach to identify, design, execute, document, monitor, control, and measure both automated and non-automated business processes to achieve consistent, targeted results consistent with an organization's strategic goals. BPM involves the deliberate, collaborative and increasingly technology-aided definition, improvement, innovation, and management of end-to-end business processes that drive business results, create value, and enable an organization to meet its business objectives with more agility.”[https://www.bpminstitute.org/articles/article/article/what-is-bpm-anyway.html]

Page 5: BPM and Scrum

Forrester Report, Prediction 2015

The Age Of The Customer Is Set To Disrupt The BPM Market:

BPM’s Value proposition shifts to customer centricity

Page 6: BPM and Scrum

6

Why BPM

■ Every organization has a number of processes. Not all are documented, neither all are followed and are up-to-date.

■ Processes change continuously, but without seeing the big picture you do not know what changes and if they are improvements or not. Most often the changes are not even documented.

■ BPM transforms this rigid pattern into flexible, choreographed business services through continuous improvement.

■ BPM improves productivity.

■ BPM improves decision-making.

■ BPM improves flexibility.

Page 7: BPM and Scrum

7

BPM and Application Development (1)

(from Craig Larman „Applying UML and Patterns“)

(p.59) „How should use case be discovered?“

Guideline: The EBP Use Case

For requirement analysis for a computer application focus on use cases at the level of elementary business

processes (EBPs).

EBP is a term from the business process engineering field, defined as:

A task performed by one person in one place at one time, in response to a business event, which adds measurable business value and leaves the data in a consistent state. E.g. Approve Credit or Price Order ..

Application Development

Business Process

Page 8: BPM and Scrum

8

BPM and Application Development (2)

„This part is usually not covered by (classic) application development!“

Business Process

Page 9: BPM and Scrum

9

BPM and Application Development (3)

Process Layer

Integration Layer

Application Development

Page 10: BPM and Scrum

10

BPM Layers

… BPM Provides Managed, Flexible Process

Page 11: BPM and Scrum

11

BPM and ERP

■ In a SOA implementation the process layer contains the process (workflow) logic. The traditional Electronic Data Processing (EDP) is done in the Application Layer.

■ A change in the process does not mean a change in the Application layer. And vice verso.

■ ERP without BPM is like the workflow in the brain with lots of email, phone calls and thus error prone and as can be often seen in the real daily work of companies.

■ Adding the BPM layer removes many manual tasks and implements the notify observer pattern.

■ The user is guided through the process without having to remember all the process steps.

Page 12: BPM and Scrum

BPM and ERP Example

BPM

ERP

Page 13: BPM and Scrum

13

Traditional BPM

In most cases this was done in a waterfall approach. Getting the requirements, modeling the processes, implementing the processes on proprietary process servers.

■ Analyze

■ Design / Modeling / Improve Process

■ Change Organization Structure

■ Implementing

■ Deploying

■ Execute

■ Monitoring

■ Optimization

■ Re engineering / Continuous Improvement

Page 14: BPM and Scrum

14

Agile BPM as Software Engineering Discipline (1)

■ Agility in BPM can be seen from different viewpoints:

– Agility as synonym for flexibility. This means that BPM is flexible and allows quick adaptation of changes in the business environment. Thus it is not related to BPM methods.

– Agility in the sense of merging modeling and implementation phases of the BPM Lifecycle.

– Agility in connection with process development / adaptation

■ To use agility as synonym for flexibility of BPM just adds to confusion.

Page 15: BPM and Scrum

15

Agile BPM as Software Engineering Discipline (2)

Page 16: BPM and Scrum

16

BPM Analyzes and Implementation method: Scrum

Page 17: BPM and Scrum

AntWebsystems PAAS Vendor view

Page 18: BPM and Scrum

AntWebsystems PAAS Customer view

Page 19: BPM and Scrum

AntWebsystems Scrum System Backlog List

Page 20: BPM and Scrum

AntWebsystems Scrum System Backlog Item Detail View

Page 21: BPM and Scrum

21

BPM and OfBiz at Antwebsystems (1)

Top Level Process of BPM and ERP

Page 22: BPM and Scrum

22

BPM and OfBiz at Antwebsystems (2)

Backlog creation sub-process

Page 23: BPM and Scrum

BPM and OfBiz at Antwebsystems (3)

The BPM sprint (1)

Page 24: BPM and Scrum

24

BPM and OfBiz at Antwebsystems (3)

The BPM sprint (4)

Page 25: BPM and Scrum

25

BPM and OfBiz at Antwebsystems (4)

BPM Tasks

Page 26: BPM and Scrum

26

Continuous Improvement

■ Is a formal ongoing approach to improve the processes (based on feedback from various sources).

■ Processes are constantly monitored, analyzed, (re)modeled and implemented

■ Reflects the actual situation.

■ allows the identification of wastes as the appear. Any changes needed are sent as a request to the product owner as described before and the agile BPM process starts for those changes to be realized.

Page 27: BPM and Scrum

27

Summary

■ BPM Projects and Scrum work well, with or without IT involvement

■ There is no need to wait for BPM to complete once the process is improved and activities are to implemented.

■ The BPM backlog is the input for the realization in ERP. Basically an activity in BPM can become a backlog item in the ERP process.

■ The same process is used for continuous improvement of the process

Page 28: BPM and Scrum

Who are we: Antwebsystems

● OFBiz Market leader and one of the top contributors● More than 10 years of experience with OfBiz● Customer centric BPM drives the OfBiz customization● Agile Scrum method used for BPM and OfBiz● BOI approved, >20 employees● Automated tests, automatic deployment by customer pressing a button● Currently supporting OFBiz installations in North America, Europe and Asia

We are always looking for people and partners!http://www.antwebsystems.com

We do follow the process shown in this presentation in our company!

Page 29: BPM and Scrum

29

Q&A