Oftentimes, a Content Management System selection is part of a large-scale site migration or redesign. When a new CMS is involved, you will want to make sure to put the CMS through a proof of concept, which should be part of your CMS selection process. A migration or redesign should include these three steps if you are using a new CMS. This table highlights the differences between a proof of concept, pilot, and full migration:
|
|
1) Proof of Concept |
2) Pilot |
3) Full Migration |
|
Purpose |
Determine suitability of tool(s) |
Discover and fix issues that arise during fairly real if partial implementation |
Move off of old platform and onto new |
|
Choose another tool at end of stage |
Possibly |
No |
No |
|
Only prod a bit at the tool or just watch vendor demos |
No |
No |
No |
|
“Real” content contributors use |
Maybe |
Yes |
Yes |
|
Site visitors use |
No |
Yes |
Yes |
|
Migrate in full section of site (content, templates, functionality, etc) |
No |
Yes |
No (implement all needed for launch) |
|
Implement key use cases |
Yes (concentrating on functionality) |
Yes (for end-to-end capabilities) |
No (implement all needed for launch) |
|
Concentrate on functionality that could break |
Yes |
Yes |
No |
|
Concentrate on the “bulk” that needs to move in |
No |
No |
Yes |
|
Concentrate on load |
No (unless a key issue that could drop a tool) |
Yes |
Yes |
|
After stage, possibly quickly scrap development to start from scratch |
Yes |
Yes |
No |
|
Estimate user effort |
No |
Yes |
No |
Post new comment