Embed Size (px)
DESCRIPTION
This presentation is from a tutorial held at the J. Boye Aarhus 13 conference. See http://aarhus13.jboye.com/tutorial/the-art-and-science-of-selecting-the-right-cms/ The goal is to help you and your team understand Web Content Management technologies, architectures, and the marketplace. Janus Boye led an intensive, fast-paced and vendor-neutral introduction to Web Content Management functionality, product categories and specific vendors. The tutorial concluded with a roadmap for product selection. The 3-hour tutorial also presents a practical approach to selecting a CMS, based on marketplace realities and the experiences gained in many selection projects. While it is easy to document dozens of functional and technical requirements for a content management system (CMS), writing more requirements actually makes it harder to select a product.
Citation preview
The art and science of selecting the right Web CMS
Janus [email protected] @janusboye #jboye13 J. Boye Aarhus 13, Denmark
Gartner Magic Quadrant
What actually m
atters?
Q: What are the biggest challenges related to CMS?• Editor interface too heavy• Vendors too slow at adding new
features• Lack of support and development
from IT• Poor back-end performance• Finding good, local system
integrators• To actually leverage the technical
potential of the platform• …
Q: Which things are most important regarding CMS?• User friendly: For end-users AND
editors• Time-to-market• Performance and stability• Flexibility and open architecture• …
”People don’t want a drill machine,they want a hole in the wall”
- Philip Kotler
Insights
from
MMT Digital
1. Getting started
Homework for customers
• Editors, content and information• Time-to-market• Project plan• Strategy & governance• Internal ressources• Unique requirements• Budget• Technology stack• Stakeholders• Project methodology• Interoperability
Who should be involved?
• IT• Communications• Marketing• Web team• Legal + procurement• Management• ?
xxx
Making decisions
PS: Budgetxxx
Budget
PS: Learn from othersxxx
Learn from others
• Is it just a CMS project for a web site?• Is it only for the intranet?• Mobile-first?• What are the expectations of the project?• Including a blog or newsletter solution as
well?
Boundaries
Lou Rosenfeld: ”Marrying Web Analytics and User Experience” (J. Boye Philadelphia 2009)
• How to be smart about gathering the requirements?
New requirements
• What’s the characteristics of good tender / RFP?
New tender / RFP
”The nice thing about standards is that there are so many of them to choose from”
Andrew S. Tanenbaum
Insights
from MOC
• What’s the characteristics of a winning proposal?
New proposals
Don’t let vendors rush the decision!
• You're the boss• Consider it a job interview
Risks
2: Process overview
WHICH IS THE LEADING
CMS?right
for us
WHO WILL BUILD IT?
10 PAGES
About the organisation
Project details, scope and goals
Project timeline
Important use case scenarios (max 10)
Selection criteria
Vendor-related requirements
Related projects
Characteristics and technical architecture
CONTENT
OPEN SOURCE
SYSTEM INTEGRATORS
License models and pricing
xxx
Scenario 1 Scenario 2 Scenario 3Vendor A OK OK OKVendor B - OK OKVendor C - OK -Vendor D OK OK OKVendor C - - -
SCORING
Demo & test drive
xxx
Tips for the process?
xxx
Wrap up:
Process
Insights
from
Folketinget
xxx
3: Marketplace
…?Easy to
customise
Fast
Easy to
use
”Trust, but verify”-Ronald Reagan
2007 elephants:- EMC- IBM- Interwoven- Open Text- Oracle/Stellent- Vignette
2013 elephants:- Adobe
- Autonomy (HP)
- EMC- IBM
- Microsoft- Open Text
- Oracle
• Composite• Drupal• Dynamicweb• EPiServer• Microsoft SharePoint
• Plone• Sitecore• Synkron Via• Typo3• Umbraco• …
Local markets
• CoreMedia• e-Spirit• Getit / Onion• Imperia• Infopark• OpenCMS• Pirobase• RedDot (Open Text)
• SDL Tridion• Typo3• …
Local markets
What about XYZ?
xxx
How to navigate the marketplace?
xxx
Wrap up:
Marketplace
Janus Boye, J. Boye
@janusboye +
The international communityfor web and intranet professionals
