I have worked with Web 2.0 technology for quite a few years now. I think the least realized value of Web 2.0 technologies is process flow improvement. For some reason (may be over marketing about how 'cool' Web 2.0 is), Web 2.0 technologies are overlooked when considering Enterprise applications. On the other hand, I tend to strongly believe that Web 2.0 is a best fit for enterprise applications.
As technologists assisting business, it is our job to take the experience of Web 2.0 past the wows, oohs and aahs into 'Hey that just decreased the number of errors a user could commit in the process'. Yes it is not glamorous. But, hey, who said it would be, right? IMHO, the best way to elicit this value in a very short time frame, is to take the most cumbersome process use case and narrow down on tasks that a user is most prone to make mistakes and then use Web 2.0 technology to guide the user through the process and hence make it a straight-line scenario.
The above approach also allows the analyst/re-designer to understand the business rules and isolate them out instead of weaving them into the view or controller. Once isolated these rules could be packaged separately into a utility library that could be ported to other applications or be exposed as stateless services or incorporated into a rules engine.
From the few years I have put on as experience, I can tell that there are many many opportunities to do this.
Go out there and have fun doing this... cheerios.
Thursday, September 24, 2009
Monday, July 6, 2009
BPM and Why...
I have been reading many blog posts and articles about BPM and EA. BPM, in particular. I have a hard time understanding why there are so many articles explaining why BPM is important. Isn't it common-sense to organize the process by which a business runs and analyze it to see how to make it better, notations and the methodologies aside. The good news from all the reading is that BPM is very well accepted/practiced in Europe and AsiaPac. The better news is that the recognition is on the rise in the US.
In my opinion, BPM should be an integral part of every Enterprise Architecture effort. Enterprise architecture is in place, after all, for one sole purpose - To make all the moving parts in an organization oriented towards one goal i.e. accomplish the corporate strategy. If the corporate strategy could not be represented in a model, then there are some missing pieces.
On the other hand, if the business leadership does not fully understand the positive impact BPM could have on the organization, then it would be a hard sell to introduce BPM in the mix. I think if we could come up with a Primer/Introduction to BPM for the Business Leaders course (may be 1 to 3 days depending on the audience maturity level), it could be a good start to help the leadership understand the need for BPM especially when it comes to companies with business process that has evolved over decades.
Let's push things forward.
In my opinion, BPM should be an integral part of every Enterprise Architecture effort. Enterprise architecture is in place, after all, for one sole purpose - To make all the moving parts in an organization oriented towards one goal i.e. accomplish the corporate strategy. If the corporate strategy could not be represented in a model, then there are some missing pieces.
On the other hand, if the business leadership does not fully understand the positive impact BPM could have on the organization, then it would be a hard sell to introduce BPM in the mix. I think if we could come up with a Primer/Introduction to BPM for the Business Leaders course (may be 1 to 3 days depending on the audience maturity level), it could be a good start to help the leadership understand the need for BPM especially when it comes to companies with business process that has evolved over decades.
Let's push things forward.
Subscribe to:
Posts (Atom)