Complexity versus Difficulty

On software development projects people have to estimate the effort involved. In doing so, one of the things analysts are asked to consider is the complexity of a process, but it surprises me how often analysts confuse complexity with difficulty.

The two concepts are mutually exclusive. A process can be simple, […]

Introduction to the BPMN 2.0 Level 1 Palette

The slide deck below is an introduction for process modelers to the Level 1 Palette of shapes for Business Process Modelling Notation 2.0.

When I was new to the BPMN palette years ago, I used it as I had used any other process flowcharting palette previously, i.e., I used the shapes […]

Process Model versus Process Map

When it comes to describing business processes BPMN 2.0 is my notation of choice.

This post is about what I mean when I say “process model” and “process map”, so let’s not get hung up on the terms themselves. If you are an advocate of and expert in BPMN and you […]

Collaboration does not equal ochlocracy

Collaboration isn’t some kind of Arthurian round table. It’s not about everyone having their say or having equal weight assigned to their say.

I have no time for the old style of business analyst who spends months crafting 3,000 pages of text (but not a single model) to describe requirements and […]

Defining process scope

Before attempting to model a business process, you should first define its scope so you know how it starts, how it ends and whether it is really one process or many.

Customer Journey

There’s a film from 1985 called The Journey of Natty Gann.

“In the 1930s, a tomboyish girl runs away from her guardian to join her single father who is 2,000 miles away, because there was work there.”

Judging by the title, I think it’s reasonable to expect Natty Gann to be the protagonist and for […]

BPMN in Pegasystems PRPC Flow Rules

There is a perception that Pegasystems PRPC can be used to create BPMN-compliant process models. However, I consider this perception to be incorrect.

This slide show takes you through my reasoning, but I can sum up my conclusion with a golf analogy:

No matter how good your 3-iron is, you can’t turn it into an […]

Process, data, decision: the triumvirate of business modelling

Many analysts have a grounding in grounding in one main area of business analysis, such as process modelling. However, a company’s business architecture cannot stand on a single leg.

In fact, three legs are required:

Process model Data model Decision model

I have seen many software development projects where […]

How do you explain re-use?

I was taken aback recently when someone told me they didn’t understand the concept of re-use.

You see, when I started out in software development, I was taught this concept, so I cannot imagine a world without it. Of course, I am not insensitive to other people’s situations, so I understand […]

PRPC Case Types

Case Types are a key element in Pega BPM development and it is important for Pega Business Architects to have an understanding of them.

Case Type is what Pega used to call a Work Type prior to Pega 7. Although the Type is a Pega implementation device, the concept also has […]