SharePoint

..as a Workflow Management System

ANDREAS ASCHAUER, ALEGRI INTERNATIONAL

SHAREPOINT AND PROJECT CONFERENCE ADRIATICS 2013

ZAGREB, NOVEMBER 27-28 2013

sponsor
s

About..

Andreas Aschauer

Alegri International
Austria
Head of Consulting

Software Engineering
SharePoint
Trainer / Consultant

Agenda

The road to 13
From Coding to Modelling

BPM and Process

Orientation

We are having a baby

A quintessential sample

Motivations for BPM

Procedures vs. Practices

(some of you can relate

to)

Why am I telling you this ?

SharePoint has a strong background in

Workflow Management

Why am I telling you this ?

Business Process Management (BPM) is

one of the key drivers for SharePoint
investments

Why am I telling you this ?

Workflow Management in SharePoint

has come a long way and changed a lot

Why am I telling you this ?

You can do so much wrong with

Workflow Management / BPM

THE ROAD TO `13

Workflows with SharePoint 2010

Visio 2010
SharePoint Designer 2010

Visual Studio 2010

3rd Party

Process

Visio 2010

SharePoint Designer 2010

Visual Studio

Impedance Mismatch

High Project Risk

Volatile Cost of Ownership
No common model or language for business and
technology

Workflows with SharePoint 2013

Visio 2013
SharePoint Designer 2013

Visual Studio 2021

DECLARATIVE MODEL

3rd Party

Visio 2013 Process View

Visio 2013 Workflow View

Visio 2013 Workflow View

Visual Studio 2012

Key improvements - General

Model First

No Code in Workflows

Process Manager &

Workflow Designer

Key improvements - Technical

Architectural Changes

Cloud Ready Model

Reusable Workflow
Actions
Reusable Designer
Actions

Wrapping Up
SharePoint OOB Workflow Capabilities have matured
The tooling has matured
Business and technology have a common modelling base
Software architecture is modular and reusable (through
Activities)

BUSINESS PROCESS MANAGEMENT

Key Motivations
Make implicit processes visible and manageable
Optimize processes continuously
Optimize existing resources
React to change

Broadening the view

Process Improvement Process

Procedures vs. Practices

Optional accessoiries

What you get..

Monitoring of (possibly) a large number of workflow
instances
Reports on performance of workflows / stakeholders
Little impedance mismatch (depends on product)
Better EAI functionality

SharePoint Workflows

No further advance cost

Unpredictable future cost

Easy to use / Familiar tooling

Clean architecture
Supported by MS

Limited OOB functionality

Complex expansion model
Custom development
needed

BPM Tools

Controllable Cost of Ownership

Advance cost

Rich modelling capabilities

Training effort

Large toolbox around BPM

(Possibly) proprietary
notation

EAI functionality
Need

Workflows

BPM

Intra department processes

Inter department and

corporate processes

Little to no dependency on
external systems

System integration

Small number of workflows

Large number of workflows

.NET development knowledge

No development resources

DEMO: Were having a baby

process
Stakeholders
Mother
Father
Grand mother
Friends of father
Doctor
..

Systems
Family
Administration
Hospital

B(aby)PM scaling out the family

Adapt to changes in systems influencing the process
Dynamically re-assign stakeholders
Optimize the process
Report on performance of closed instances

Know the options

Do Governance planning

Calculate the risk and total cost of

ownership

Have a baby..

questions?
LINKEDIN / XING / SHAREPOINTTRENCH.COM

@ASCHAUERA

thank you.
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS 2013
ZAGREB, NOVEMBER 27-28 2013