We have a number of scenarios we'd like to enable in future releases of Visual Studio Team Foundation that would really benefit being part of a generalized workflow framework.  Things like code review/checkin processes, build release and staging, etc.  And no matter how many scenarios you cover, customers will always come up with more.  Building workflow into a system can be hard enough without having to make it extensible too.  Fortunately, Microsoft is working on the Windows Workflow Foundation as part of WinFX.  This looks very promising.  One of the folks on the team, Mark Schmidt, has written an authoring tool that looks interesting.

A company I worked for many years ago developed a huge workflow system for OS/2 and Unix so I've always been intrigued by this stuff.  It was ginormous and had all sorts of memory limits, usability was poor (it used lots of non-modal windows - and I mean lots), and everything was so darned generic that as a user you really had too much of the implementation exposed to you.  The problem is that it was a generalized engine that wasn't really a proper API that had a GUI slapped on top of it.  When what you really want is an engine that manages the flows and allows you to build a tailored customer experience that is relevant for your scenarios.

Stay tuned...