In a break from the KM roll I’ve been on, I see that Craig at Better Projects has dipped his toes into one of those religious debates: to use process models or use cases (here)? SAP always has had a strong
project process bias, but eSOA and custom development concept is forcing a shotgun marriage of the concepts. A couple of comments:
Per Craig’s post, process is a useful anchor for use case-driven innovation.
That anchor faciliates the eventual commoditization, operationalization, or productization (choose your own awkward formulation) of the innovation into a repeatable, standard process.
More SAP customers expect us to deliver ERP and other packaged solutions, compose and develop services, and code custom development simultaneously.
The expectation is driving us to align structured and agile/iterative methodology approaches (to deliver in a project, program, etc.).
Of course, RUP claims to marry the two approaches (see here), but slapping a “swim lane” overlay on a process map begs the “agile” question. Does this really oriented one towards “individuals and interactions” over “process and tools” (www.agilemanifesto.org)?