CMS Proof of Concept, Pilot, Migration
Submitted by David Hobbs on 29 October 2009 - 7:48am
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 |
| Concentrate on migrating in only one full section of site (content, templates, functionality, etc) | No | Yes | No (implement all needed for launch) |
| Implement only 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 |
Bookmark/Search this post with
Recent Posts
- RT @SAI_Tools: Only Half Of Kindle Fire Customers Are Totally Happy With The Device $AAPL by @_dtl http://t.co/SdfG7P3R — 1 day 3 hours ago
- \"Top 6 List of Programming Top 10 Lists\" Especially like Obasanjo\'s list http://t.co/Vw6lgGzt — 1 day 5 hours ago
Thanks Tim. I updated the
Thanks Tim. I updated the table to clarify. The point was that the full migration should concentrate *only* on one full section or subsite, and *only* key use cases. Definitely the full migration would continue on the key use cases and all subsites, but hopefully by that point the key use cases would have been thoroughly vetted and one full site section had been migrated in to see any issues (before all went in).
Overall, very useful. Can you
Overall, very useful. Can you better explain why you have "No" under Full Migration for "Migrate full section" and "Implement Key Use Cases"? It seems in both cases you are saying all relevant WOULD be in. Perhaps you mean the row titles to specify samples of full sections and key use cases? Or am I missing something?
Post new comment