[CM Briefing]
[Edge] Home > Papers > Time needed to select a CMS Contact | About | Search [Edge]
 
[Printed Version] [Document in PDF Form]
(72kB PDF)
  
 
[Related Papers]
[Bullet]Latest Papers
[Bullet]CM Briefing
[Bullet]Content Management
  
 

[Find out when new papers are published.]

  
 

[Upcoming Seminars]

  
 

[Intranet Innovations 2007]
Intranet Innovations 2007

  
  
Interested in syndicating our articles?
Find out more
  

CMb 2008-01
Time needed to select a CMS

by James Robertson
Published on 8 February 2008

It will always take longer than hoped to select a new content management system. While an 'accelerated' approach can be taken, the reality is that somewhere between 6 and 12 months will probably be needed, from beginning to end.

To help clarify this statement, this briefing provides a breakdown of the individual steps and the amount of time needed for each. Use this to set appropriate stakeholder expectations, and to develop a realistic project plan.

Selecting a CMS: step-by-step

ActivityDuration
Redesigning the site8 weeks
Making a business case4 weeks
Receiving project sign-off, approval4 weeks
Documenting CMS requirements2 weeks
Preparing tender/RFP, getting final sign-off4 weeks
Providing tender/RFP to vendors, obtaining written responses3 weeks
Reviewing written responses, determining a short-list2 weeks
Vendor demonstrations, including advance notice for vendors3 weeks
Vendor evaluation, final decision2 weeks
Final management sign-off2 weeks
Contract negotiation8 weeks
TOTAL42 weeks

The table above shows the individual steps involved in selecting a CMS. While these will vary between organisations, typical selection processes will involve the majority of these activities.

A few notes on the table:

  • The times shown in the table are elapsed time, not effort.
  • The total at the end of the table is a sizeable figure, the result of many small numbers adding up. There are no major time costs at each step of the process.
  • The starting point is to conduct a high-level redesign of the site before documenting the requirements, as the site design is a selection criteria for the CMS.
  • Time needs to be allocated for vendors to respond to the tender/RFP document, as well as enough advance notice of the vendor demonstrations.
  • One vendor demonstration will be held per day, with an assumed final short-list of three vendors.
  • This is an 'accelerated' selection process, only possible with the right in-house skills or professional support. For example, documenting CMS requirements in only two weeks would almost certainly require the assistance of a specialist CMS consultant.
  • In reality, further time is likely to be lost due to internal politics, procedures or bureaucracy. Sign-off processes are often a major bottleneck for these types of projects.

Your mileage may vary

Feel free to adjust the times in this table to match the realities of your organisation. Some numbers will go down, and a few steps may vanish entirely. Some numbers will almost certainly go up.

Either way, there will be no way of getting the timeframes below 3-4 months, even in the best case. There are simply too many individual activities for that to be possible.

Fundamentally, the goal of this briefing is not to specify the definitively 'correct' times, but to give a simple model to help project teams estimate project durations for themselves.

The better this can be done at the outset of the project, the more likely the project is to finish on time, while still delivering the desired benefits.

Printed version of this article (PDF)

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