Home > CMS Lifecycle

Contact | About | Search

	This section outlines The CMS Lifecycle, a simple model for the overall process of developing and managing a content management system (CMS). We have developed this model as part of our commitment to providing insight, structure, and support for all aspects of content management. Goals & Requirements The need for a content management system is identified, and the overall business goals are determines. A comprehensive requirements process then identifies the specific business needs that must be met by the CMS. Related information: How to evaluate a content management system Content Management Requirements Toolkit Losing sight of the content in a content management system Centralised or decentralised authoring? What are the goals of a CMS? Sixteen steps to a renewed corporate intranet Area Health Service Project (weblog) Metrics for KM and CM Why every small website needs a CMS       Evaluation & Selection Once the business requirements have been identified, research is conducted to find products that will meet these needs. This evaluation process normally ends in an open tender for a CMS vendor and product. This phase is complete when all legal and contract details have been finalised, and a CMS is purchased. Related information: How to evaluate a content management system Australian CMS vendors CMS vendor lists Choosing the right content management system (seminar) Buy or build? (weblog entry) Development & Deployment With the purchase of a CMS, work now begins on the development of a tailored solution for the business. This includes establishing the IT infrastructure, conducting training, information architecture and usability. By the end of this phase, the full range of CMS issues has been addressed: technology, people & processes. Related information: Losing sight of the content in a content management system Deploying an effective search engine NRMA Case Study RTA Case Study Phone directory first; CMS second (weblog entry) Authoring options (weblog entry) Putting metadata to work Techniques For Building a Better Intranet         Growth & Expansion Once the project phases have been completed, a structure is put in place for the ongoing management of the CMS. The CMS is then progressively rolled-out to the rest of the business, and to encompass the complete range of content. This is a "make or break" phase in the lifecycle. If it is successful, the "fully integrated" phase is reached. If the CMS is not sufficiently supported and evangelised at this point, there is a danger that it will languish. Without business support, CMS usage will fall, content will become out of date, and the CMS will be effectively "moth-balled". At this point, the project has failed, and the CMS Lifecycle starts again from the start (requirements, through to purchase and deployment). Related information: How to revive a zombie content management system Fully Integrated This is the end goal of a content management project. The CMS is now a normal of daily business operations, and is fully integrated into the organisation. The CMS meets all business goals, and is supported by effective people & processes. Furthermore, a strategy of "continuous improvement" ensures that the CMS evolves in step with business directions and strategies. Related information: Avoiding the same mistakes (weblog entry)

	For questions or comments please contact the Webmaster. Last updated 15 March 2004. © Copyright 2004, Step Two Designs Pty Ltd, ABN 99 081 019 623. All rights reserved. Intranet Peers and Intranet Roadmap are trademarks of Step Two Designs.