What to Expect When Implementing a New CMS
Apr 23, 2012
When implementing a new CMS, it’s easy to get caught up in all the bells and whistles of the platform without considering the basic implications of a new system. What type of development method will you use? Who will own the project? How will you get everyone on the team on board? How to plan for the unexpected costs? How will you make sure everyone has the training and support they need.
Different Development Methodologies
- Waterfall – sequential development approach through Analysis, Design, Implementation, Quality Assurance, Integration, and Maintenance.
- Incremental – breaks a project into smaller segments, reducing risk by working on smaller segments; also allows for some development flexibility.
- Agile – iterative and incremental development where requirements and solutions evolve through collaboration between self-organizing/cross-functional teams.
The Need for a Product Manager/Owner
Avoiding Adoption Issues
- Clearly outline your goals and objectives
- Involve your site users and editors during the Design Phase
- Show your editors how your new CMS will make their day-to-day tasks easier
- Offer support and training – this is paramount, but often overlooked
Different Users = Different Training Needs
You will Need Support
Software Development Methodology (Wikipedia)
Agile Software Development (Wikipedia)
Why Could Your CMS Implementation Fail? (SlideShare)