Welcome to the new incarnation of BPM Blog.
Two weeks ago, the company I worked for (Fuego) was acquired by BEA Systems. In one of my blog posts about the acquisition, I questioned what effect the acquisition should have on BPM Blog. Should I keep BPM Blog independent, or should I make it a part of BEA's Dev2Dev blogging site?
In response to the rhetorical question, I got an invitation to join the ebizQ blogging team. Obviously, I accepted the offer. I knew from my web server logs that many of my readers were ebizQ readers, so joining the ebizQ bloggers seemed a natural fit. (Especially given how much I've been linking to Column2 over the last couple of weeks.
For those of you who are new readers, you may want to to check out the archives at BPM Blog's original home: http://www.bpm-blog.com . I plan on keeping the original site around until I can get all of the content imported into the ebizQ system.
For those of you who are already readers, and are following the link over to here, thanks for reading. You may want to change your feed readers over to the new feed if you are using an RSS reader. Pardon the typical migration struggles as I try to resolve all of the stylesheet issues.
To re-introduce myself, I'm a BPM Systems Engineer. I work for BEA Systems in the Business Interaction Division, which includes the AquaLogic Business Process Management products (formerly FuegoBPM). This means that spend most of my time working with customers in pre-sales. Basically everything from speaking engagements to customer demos to implementation planning and architecture.
In addition to blogging about the BPM industry, I've been known to stray offtopic to discuss the Getting Things Done productivity methodology, the technology industry in general, and even weightlifting. One of the conditions of joining ebizQ was that I post more regularly. Which means that I'll have even more chances to be offtopic. :-)
So check this space in the coming weeks. I'll be posting some more thoughts about the BEA acquisition of Fuego as well as some posts about exactly what I think the future of BPM may hold.
Leave a comment