All process improvements are not created equal. How should we select which processes (or process steps) to improve? How do we approach this for a really large migration project? Start with understanding the potential for improvement and then narrow it down from there.
Flesh Out Those Wireframes
Stephen Turbek, at Boxes and Arrows, tells us how to get better results from our wireframes. Wireframe prototyping can provide feedback early in the design cycle, reducing costs and improving the quality of the final software. By putting a little flesh on the bone, we can get even better results.
Process 2006 – Day 1 by Sandy Kemsley
Sandy, of Column 2 fame, is blogging the Process 2006 convention “live” as it goes. Subscribe to her blog to stay on top of things. For now, here are the articles she’s posted from day 1.
BPMN Deadlock
One danger of using a precise language like BPMN to describe business processes is that you can precisely get yourself into trouble. Deadlock (in BPMN) is a condition used to describe a process that can’t be completed. By designing (or describing) the wrong business process, you can create a process that never finishes.
Before And After – A Rule For Improving Processes
Nils proposes his rule of three boxes as a consideration when developing software or software features to improve business processes. In short, make sure that you can actually execute the new process. It isn’t enough to create a good “replacement process” – you have to be able to transition to the new process and then back out of it. The new process is plugged into a business ecosystem, and it must coexist with the existing processes.
BPMN Compensation Event Correction
One of our readers (thank you!) pointed out that another blogger was critiqueing one of our earlier business process modeling notation (BPMN) diagrams. Turns out we made a couple mistakes. Here’s a more detailed look at the compensation end event.
Carson Didn’t Work On Fridays
And this week, neither do we. Have a great weekend, see y’all at our regularly scheduled time next week (every weeknight). Scott
BPMN Diagrams – Sequence Flow
BPMN Diagrams don’t use the term control flow to describe processes. They use the terms sequence flow and message flow. Within sequence flow, there are four classifications of flow.
BPMN Diagrams – Intermediate Multiple Events
We can simplify BPMN Diagrams with intermediate multiple events. These events are combinations of different intermediate events, much like complex gateways combine different gateways.