Content Management System Timeline

1
Content Management System Timeline

• Jun 1998 Start market research
• Sep 1998 Select Interwoven TeamSite
• Mar 1999 Launch ver. 2.5
• Aug 2000 Upgrade to ver. 3.1
• Jul 2001 Upgrade to ver. 4.5
• Part of major site redesign
• Metadata integrated into workflow, DataDeploy to
  Oracle
• Java code maintained in TeamSite
• Jun 2002 Upgrade to ver. 5.0
• Development staging servers
• Templating (content presentation)
• Simplified author interface front office tools
• Improved workflow builder

2
Most Recent Upgrades

• Sept 2003 Upgrade to ver. 5.5.2
• Reorganization of files into Branches that mirror
  web site path
• Added administrative tool (I.e. Admin Delete,
  Custom Unlock)
• Added DEV and TEST environment
• May 2005 - Version 6.5
• Support for current version was ending
• Migrate existing functionality while minimizing
  change

3
Issues

• CMS Software
• Product bugs limitations
• Customizations
• Necessary to adapt product to agency needs
• Must develop own procedures, documentation
  training
• Complicate version upgrades
• Version creep
• COTS but not-COTS vendor consulting services
  hard to avoid
• Content freeze (no good time)
• Compatibility
• Licensing
• Vendor support continuity
• ED
• Staff skills
• Management expectations

4
Lessons Learned

• Customizations dont always carry over
• Timelines can be unrealistic (need to include
  enough time for problem resolution)
• Dont assume that all tests will run smoothly
• Budget needs to include enough money for vendor
  support to help with rough spots during testing
• Double whammy redesign plus upgrade. Keep tasks
  separate if you can.

5
Lessons Learned (cont.)

• Create a separate test environment that mirrors
  your production site
• Create a test plan that encompasses every single
  piece of functionality
• Test with real user roles not just administrator
  role (because they have rights others dont)
• Have real CMS users run through sections of the
  test plan (not just developers) because they will
  spot oddities that developers will miss
• Develop a timeline that allows for testing (and
  re-testing!) all of your functionality
• Develop a budget for the upgrade that includes
  development/re-development of customizations