Every collaborative system needs some way to notify people of things that need attention. Email is by far the most ubiquitous option for reaching out to people. Done well, email is an effective way to draw people in to work they need to do. Done poorly, and the email is an annoying waste. What is needed to do it well? Continue reading
We demonstrated a service mesh architecture approach for BPM and Case Management in order to show that the Fujitsu DXP product could scale to any size and performance desired. First we started 12 million running process instances, and then we simulated 3000 users hitting those server, and while that was going on, showed that a work list could be retrieved — for any of the 3000 users — in less than 2 seconds. How did we do this? Read on.
Stung again, several times in one day. Systems that fail to report problems can waste everyone’s time. The problem is that such system appear to be running fine, and that is great for lazy programmers and product managers alike. Just . Say . No .
Standards always seem to move at glacial speed, so slow it is hard to see any change, but looking back over the past decade or so, we can see the JSON has won the internet format battle, and XML is a thing of the past. Continue reading
A co-worker on an agile project was showing me a feature he was perfecting, and it was looking pretty good with features to add and remove various settings as per the design. I wanted to try it. He said “sorry, the create function is not implemented yet.” It got me thinking…. Continue reading
Selling big complex products is always a challenge. I recently was asked why not make the product simply available on the cloud for free sign-up and access so that people can try it out for free. Here is my response. Continue reading
I run large complex software projects. A naive understanding of complex project management can be more dangerous than not knowing anything about it. This is a recent experience. Continue reading
Peter Schoof interviewed me last week on the subject of robust BPM. (Thanks Peter!) This had been the basis of a talk I gave in Montreal at the Workshop on Methodologies for Robustness Injection into Business Processes. It is a quick 15 minute summary:
Too much of a focus on the on the business process can cause a business solution to be poorly designed and problematic. This is a story from several customers who followed the BPM methodology too well, and were blindsided by some nightmarish systems issues. Too much process can be a real problem. Continue reading
Here are my notes from the second day of bpmNEXT on March 31, 2015. Note: I spoke on day 3, so was too busy, so these conclude my notes of the event. Continue reading