A great opening pop video – let’s see how far we’ve come. How far we’ve come is reflected in that a vendor gets to have more delegates at their own conference than the mighty Gartner. 850 people all gathered and sitting together to discuss their respective journey’s and approaches.
Alan starts off with a couple of anecdotes about history of Pega and how they started on Main St. Product has now gone through 4 from scratch rewrites – yet the core vision of the company is still very much aligned. A lot of M&A activity has led to an evolving landscape of customers – JP Morgan Chase now represents some 10 original Pega customers.
I see that Alan’s 6 Rs have been there for a very long time too (and I am still not sure that these 6 Rs do anything more than confuse poor Caddie the Customer). The core message – about Process Automation – where the business and IT learn to work together. All about allowing them to change roles, which is a little frightening for most. And a lot of this change of roles is about persuading IT folks to allow business people to get involved in real world implementations. It’s not about the IT and data, its about the business and their ability to get things done.
There is no layer to BPM – neither is there a rules layer … it is more like a DNA that needs to live in the body politic of the organization. Yes, how you control it and how insert it into the organization needs careful thought, but it is not some part of a stack on an IT architects chart.
Mind The Gap
The requirements specification is a dead and outmoded way of thinking about systems that hasn’t changed since the mid-sixties (something I have been saying for yonks). Its about allowing the business and IT people to work together, so that instead of starting with documents, the approach lets you generate documents as recordings of the state at that time in your thinking. It’s far more effective to use a model driven environment to support that – it’s also cheaper and quicker.
But the IT folks have human beings acting as some sort of typing pool to translate conversations about business intent into some sort of arcane language. Automating the programming is not sufficient – we (Pega) want to automate the business logic. You have to capture the entire user intent. This is not about putting a Pega system on the desktop, it’s about putting the user intent on the desktop.
Platform as a Service – enabling people to set up an entire Pega system for a part of their organisation, they can create their own SaaS enabled applications doing it easily and directly. To use Pega to put parts into your web site … to insert Pega functionality into your web site.