1. Factors to consider when selecting a CMS Or, why features lists shouldn't drive your CMS selection process
2. Agenda Introductions Lack of choice isn’t the problem: a look at what’s out there ‘One size fits all’ doesn’t apply to CMSs, nor should it apply to the evaluation process CMS selection process must haves: Business objectives (vs features lists) Narrowing the field User stories/scenarios (vs functional ‘requirements’) Demos 19/08/2010 Selecting a CMS/LG Web Network 2
3. Who I am Malini Raha malini.raha@gmail.com @atomic_anu 0448839716 19/08/2010 Selecting a CMS @ LG Web Network 2010 3
5. A look at what’s out there Sources of information Industry reports What counts as a CMS CMS paradigms CMS vendors & implementers 19/08/2010 Selecting a CMS @ LG Web Network 2010 5
6. Sources of CMS information http://cmswatch.com http://cmswire.com http://cmsmatrix.org 19/08/2010 Selecting a CMS @ LG Web Network 2010 6
7. Even more info on CMSs Forrester Wave Gartner Magic Quadrant 19/08/2010 Selecting a CMS @ LG Web Network 2010 7
8. Sources of CMS information Other councils Australian Overseas 19/08/2010 Selecting a CMS @ LG Web Network 2010 8
9. What counts as a CMS 19/08/2010 Selecting a CMS @ LG Web Network 2010 9
10. What counts as a CMS solution 19/08/2010 Selecting a CMS @ LG Web Network 2010 10
11. CMS paradigms Understanding different models, unlikely to be a selection factor for local governments & councils: Front end / back end Delivery on request / delivery on publishing Multi-site / federated Open source / proprietary Hosted / installed 19/08/2010 Selecting a CMS @ LG Web Network 2010 11
12. CMS vendors Local Australian vendors (107) & international CMSs in Australia (35) source: http://www.steptwo.com.au/resources/australian-cms also, Open Source products 19/08/2010 Selecting a CMS @ LG Web Network 2010 12
23. Narrowing the field Lot’s of options, begin filtering Based on technology Based on budget Based on project management processes 19/08/2010 Selecting a CMS @ LG Web Network 2010 18
24. Technology Hosting environment Platform Legacy systems Integrating with other applications 19/08/2010 Selecting a CMS @ LG Web Network 2010 19
25. Technology Hosting environment Platform Legacy systems Integrating with other applications 19/08/2010 Selecting a CMS @ LG Web Network 2010 20
26. Budget License fees Service fees Total cost of ownership 19/08/2010 Selecting a CMS @ LG Web Network 2010 21
27. What are you looking for in an implementer? Delivery model/process Quality Assurance Deployment procedure Service Level Agreements 19/08/2010 Selecting a CMS @ LG Web Network 2010 22
28. User stories vs functional requirements Examples of functional requirements “A2.1.1 Ability to establish a variety of roles within a workflow processA2.1.2 Ability to assign, grant or withhold workflow permissions to specific roles or individuals.A2.1.3 Provide workflow schemas that support sequential approval steps.” Instead, user stories provide scenarios how the CMS will be used “Richard enters the text for the page, and creates a link to the supporting PDF. Once the content has been spell-checked, Richard submits the page for review by Jane, his manager.”source: http://www.steptwo.com.au/papers/kmc_scenarios/index.html 19/08/2010 Selecting a CMS @ LG Web Network 2010 23
29. Other short listing considerations What’s it really about, the service provider or the CMS? Who will be implement-ing the solution? Management consultancies Digital agencies Vendor’s professional services Your in-house team 19/08/2010 Selecting a CMS @ LG Web Network 2010 24
32. Standards are nice, but elusive source: http://www.jboye.com/blogpost/10-years-web-content-management-some-inconvenient-truths
33. Demonstrations Demonstrations requested from shortlisted bidders – short list of 3 - 4 bidders Time cap – 1 hour Provide a script - build on the user stories already used in the RFT Involve representatives from groups that will interact with the CMS 19/08/2010 Selecting a CMS @ LG Web Network 2010 26
34. Summary Lead with organisational objectives Your requirements use non-functional requirements to filter should be collaboratively compiled with multiple stakeholder input – involve those who will be using the CMS express them as usage scenarios, not features/functionality matrices Demonstrations, following your script, are key Evaluations Discuss, debate, vote – important for the evaluation team to include stakeholders Qualitative vs quantitative 19/08/2010 Selecting a CMS @ LG Web Network 2010 27