This subject was introduced by a group of WCM guys and will be discussed in the best Web Conference in the world by Janus Boye.
This will include a Web Content Management track that is suggesting it will give guidance as it states
How do you get it right? What are the pitfalls to avoid? On this track you can learn from internationally recognized analysts, who will be joined by practitioners, all sharing their insights on how to get it right.
to solve your earthly problems with the WCM implementations.
The panel will be Janus Boye representing the customer viewpoint, Jarrod Gingras of CMS Watch representing the analyst massive, and Jon Marks defending the honour of the implementers.
This session will be an interactive one where you can use twitter to submit questions about the problems or solutions you had to WCM implementations using #fixwcm tag.
But what is really wrong about the WCM that we are in need of this session?
Inspired by the twitter tag #fixwcm i was pondering about the CMS sickness and what is the methods i see to cure that.
some people suggest that the WCM term is bigger then what it should be and thus too hard to handle and needs to be cut into smaller chunks.
Others put the blame on estimates and project schedules, or more politely on the sales process for cutting down on the implementation times.
But what is wrong with the WCM products and implementations?
The customer is not happy with the solutions and usually works with it only due to necessity not because they love using it.
But why is that?
The technology has matured enough to satisfy any customers need.
Implementers have matured.
The web has matured and implementation processes been formed. we have Agile methodology to make the implementation in the most versatile way.
This should have been sufficient to support the creation of the best fitting products for each and every customer. but it just doesn’t cut it.
Whats is wrong with that?
Interaction is what comes tomy mind every time i think of what went wrong.
Internal and external interactions are the place where we lose the implementation.
it starts with the initial process of selecting the right product through translation of business processes to requirements and failing of the requirements to be formed into artifacts in development and to the final grave of testing.
When selecting a product you are dealing with the Sales teams of each vendor and they want you in, that is where you get the more generic answers “Yeah our product can do that” and they are correct but it takes time to make the product do that.
Jon Marks had a discussion about the selection process. iguess there is no clear solution to this enigma.
It continues with the Dictionary each party is using through to politics and risk management.
To prove the dictionary point just ask any of your clients what CMS is, you will be in for a bit of an earthquake.
So what is to be done?
Some of the points that were up in the air like simplification of terms under the CMS with smaller chunks will create an easier dictionary.
use of simpler tools for the implementation.
The way i see it changing is with the maturity of the clients and the implementors in understanding what should be done when implementing the WCM and been trouthful about the weight and cost of such a process we will have a better implementation and love to WCM solutions.
Peace and Love