I’ve had a surprisingly difficult time conveying my own definition of “Iterative Development” in the past, so I thought I’d take a stab at explanation via analogy. Let’s compare your Business Process to a trip from Austin, Texas to El Paso, Texas.

The most important aspect of my trip is arriving at my destination.  No matter what interesting things may happen on the way, if I don’t end up in El Paso, my trip has failed.

The same is true about your Business Process.  No matter what else goes on, there is an objective to your process and you have to accomplish that objective.

Read the rest of this entry »

Recently, I was working with a client to implement a managed Loan Origination Process using Lombardi’s Teamworks BPM suite.

As with any real-world process, there were a few interesting “gotchas”, but on the whole it was a pretty standard process that many of you would easily recognize.

In this case, modeling the Loan Origination Process using BPMN diagrams was fairly straight-forward, but when we got to the point of implementing Task Assignment and Routing things got interesting. Let me very loosely paraphrase some roughly similar Task Routing requirements (that I made up for this blog entry):

Read the rest of this entry »

It is tempting to go on and on about the relationship between business and IT. Here at Lombardi we like to instead talk about effective cross-functional teams that can build the end-to-end process together. And we practice what we preach - this is why we have BPM Analysts, Consultants and Developers on our delivery teams. Note this does not mean companies have to fundamentally re-organize, but they do need to be able to create dedicated cross-functional teams if they are going to be successful.

That being said, I think that user interfaces are key to how these cross-functional teams can work together effectively. This is something that I touched on briefly in my previous post about Web2.0 and “making BPM cool again.”

Read the rest of this entry »