I’m a fervent follower of Michael Krigsman’s blog on IT failures. As you might expect, this is largely due to my morbid fascination with “projects gone bad” but it is also because I think he does a great job synthesizing current trends in enterprise application implementations. The video below, produced by SAP, speaks to rapid implementation methodologies; a trend we’re witnessing in a number of our OEM partners within Human Capital Management, Enterprise Resource Planning and Supply Chain Management to name just a few. Take a look:
It’s a good (albeit brief) summary but I’d like to add one thing to Michael’s notion of “chunking” an implementation into groups of smaller, modular projects. I concur that this is sensible, increases control, heightens visibility and helps replicate consistently, but I’d add that while separating is good, we need to maintain the connectivity between the disparate components to remove redundant efforts (e.g. building BPP and test script documents for procedures in the technical implementation, only to essentially replicate these in the form of user guides/help files later in the change management or post-go-live support readiness phases). So while ‘dividing’ can lead to ‘conquering’ the project, the most rapid and robust implementations don’t just ‘divide and conquer’ they ‘divide and connect to conquer’. Semantics? Perhaps. But as with any successful project, the devil is always in the details.
The good news? Thanks (in part) to our technology, our partners are already ahead of this curve (apologies for the shameless plug).