tag:blogger.com,1999:blog-8516720.post6620395469363281638..comments2023-10-28T07:35:54.278-07:00Comments on Knowledgeline: Microsoft worfklow gaining momentumTom Baldwin - Chief Knowledge Officerhttp://www.blogger.com/profile/17784991145294186359noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8516720.post-7619656880586859222007-07-13T10:12:00.000-07:002007-07-13T10:12:00.000-07:00Workflow is an integral component of Knowledge Man...Workflow is an integral component of Knowledge Management Initiatives. More often than not, I am approached to implement a Knowledge Management System (KMS) where the KMS is the perceived end-all to the information management problem and the process/workflow component is not on the radar. Without standardized (manual or electronic) processes, the KMS becomes a content conversion project that inevitably fails. Current content is converted and the processes for information inception to the end pristine knowledge artifact(s) are not addressed. Ultimately, adding another information silo and useless repository.<BR/><BR/>WF is code intense and free. It is not a BPM tool but a framework to code workflow processes. K2.net provides a GUI interface to model the workflow after significant coding is complete for each object. Note: I have viewed demos of the new k2 [blackpearl] version and have yet worked with it in production environment. AgilePoint provides out-of-the-box process activities, which need configuration but no code development. Of the three tools, AgilePoint is the only true BPM solution.<BR/><BR/><BR/>Research each tool for yourself and remember Gartner statistics show 85% of IT projects fail to meet objectives whereas 90% of ‘process’ projects succeed.<BR/><BR/><BR/>WF (100% Code: 0% Business Analysis) <BR/>K2 (80% Code: 20% Business Analysis) <BR/>AgilePoint (20% Code: 80% Business Analysis) <BR/><BR/>I left off MetaStorm since it wasn't a .NET code base when I trained on it.<BR/><BR/>Geoffrey Fillar<BR/>Sr. Knowledge ManagerAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8516720.post-80835962387297848342007-06-15T08:53:00.000-07:002007-06-15T08:53:00.000-07:00Development with WWF is certainly not anywhere nea...Development with WWF is certainly not anywhere near as turnkey as some of the off the shelf tools, but at the same time we were able to get a working prototype up and running within 4 weeks. So, at least at our firm, we didn't find it harder, per se, just more time consuming to do some things that aren't out of the box. Vendors adopting WWF are moving in the right direction and certainly firms should explore anything that will accelerate their workflow development.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8516720.post-91873992302232883092007-06-15T08:43:00.000-07:002007-06-15T08:43:00.000-07:00You're absolutely right about the importance of wo...You're absolutely right about the importance of workflow. The workflow approach to development builds more flexible and needs-responsive applications faster. And you're right that Microsoft Windows Workflow Foundation has changed the game. But developing directly on WWF is <B>much</B> harder than you're accounting for. Thus creating a market opportunity for companies like K2, whose newest workflow tool BlackPearl is built on WWF and provides tools for building applications <B>very</B> rapidly. MetaStorm is headed in the same direction: use WWF as the platform, add value on top.<BR/><BR/>Michael MillsAnonymousnoreply@blogger.com