Best Practices an Introduction
Best Practices is there such a thing? At the end of the day there is, but it isn’t always what you want them to be. Many of my clients look at Best Practices as the silver bullet. They expect a plethora of best practices to be immedatly implementable, and for us to come and go in a flash. Is this reality or a far flung dance with the devil?
When implementing ECM there are best practices, there are repeatable processes and frameworks from which to start. However these what I am seeing is that most of the time the Best Practices or (BP’s) as i’ll refer to the them are abondonded in favor of rapid deployments. Of these many fail outright or at a minumum fail to achive the goals set out at the onset of the project.
When I look at any ECM deployment I am looking at a program not a project. When you make that differenation you realize that to successfully implement Enterprise Content Management across an organization, there are many facets to consider to ensure success. A typical list would include, but is not limited to the following area’s to consider when defining an ECM program:
- Program Management
- Change Management
- Anayltics and Design
- Taxonomy and Metadata
- Development / Configuration
- Testing
- Deployment
- Support
The point is simple, ECM deployments are multi-faceted. There are far more criteria to invovle than the implementation of a simple application development project.
This series will drive into the deapth of these areas showing examples of where I have see programs succeed, and where I have seen them fail.
TF
