By Kat Liendgens
Friday, October 16th, 2009 at 11:30am
In Part 1 of our Keys to CMS Project Implementation Success blog series, we discussed the importance of securing early buy-in from end-user stakeholders. We talked about the importance of identifying a project sponsor to oversee the implementation and facilitate communication. Getting buy-in from stakeholders and identifying this sponsor are critical in ensuring a successful implementation. However, equally important and critical to project success is the proper identification of your project scope.
Selecting your QuickStart Package Scope
To quicken user adoption, our Services team provides our clients with a variety of options to get their websites up and running. As the name indicates, a QuickStart is intended to help organizations get a small section of their website integrated into Cascade Server. Which particular portion of the site is implemented is up to the organization, but we recommend that the section integrated is a good representation (in terms of structure and layout) of the rest of your site content. This is to ensure that the integration techniques and best practices we have implemented can be applied by your web team to future sections of your site.
When selecting a QuickStart project, keep in mind that a small project that can be accomplished within 100 hours is ideal. This project will likely serve as a "proof of concept" for viewing by anxious stakeholders waiting to see how the CMS works for your organizational site.
Although the goal is to ultimately manage all of your site and subsite web content with Cascade Server, the purpose of the QuickStart package is to take a small amount of that content and time (100 hours) to properly set-up a portion of your site using best practices that can be reused across future integrations. As always, when you continue to bring your site content into Cascade Server, if you want help along the way, our Services team is available to help with a variety of projects to maximize your benefits and minimize your costs.
Look out for part three of our "Keys to CMS Project Implementation Success" blog series coming soon, in which we'll discuss the importance of requirements gathering.
Related Content
Category
- Commentary
