Timeline
In the coming months, the project team and activity committees will focus on executing tasks associated with identifying, evaluating and selecting a Web content management solution, and with the deployment of an implementation program that will inform the development of a comprehensive, efficient and effective methodology for rollout of the solution to the campus.
Phase I: Project Definition
Winter-Summer 2007
Status: Complete
Vision and Scope document
The Vision and Scope document serves to clearly identify the business requirements being addressed by the initiative,
summarizes the intent and breadth of the proposed solution, defines internal commitments and resources and described the context
and factors influencing the project overall. This document is largely based upon the results of work conducted during the initial
phase of the project.
Phase II: Requirements and Evaluation
Fall 2007
Status: Complete
Functional and Technical Requirements
The Functional and Technical Requirements document lists the specific features and software capabilities required of the
Web content management solution as identified and agreed upon by the project team and requirements and evaluation committee.
In its final version, the document will include criteria against which candidate solutions will be evaluated and selected.
The functional and technical requirements are based upon:
- Business requirements defined within the Vision and Scope document
- Web standards, policies and guidelines adopted and promoted by the campus
- Industry best practices and known core Web content management capabilities
- Existing workflows and Web development practices
- Expressed needs, requests and recommendations made by technical staff, content managers, Web developers and communicators
- Feedback from the campus community
Identification of Solutions
The list of candidate solutions will include options that are:
- Offered by reputable, financially solvent commercial solutions providers or
- Open source systems supported by a long-standing and competent community of developers, and
- In use within departments and units at UC Davis or
- In use within departments and units at other higher education institutions or
- In use at other organizations in a capacity similar in scope and breadth to that defined within the campus's business requirements
A list of prequalification criteria will be derived from the business and functional requirements and compared against the candidate list to identify which solutions will be considered in the formal review and selection process. Prequalification criteria will reflect the features, components and capabilities that potential solutions must possess if they are to be considered viable options.
Product Review and Selection
Pre-qualified Web content management solutions will be evaluated by the Requirements and Evaluation committee using the criteria defined in the
Functional and Technical Requirements document. The Requirements and Evaluation committee will present its findings and advise the Project Team
and Steering Committee on the selection of a solution for testing and implementation.
Phase III: Implementation
Spring 2008
Status: In progress
Implementation
Under the leadership of the Implementation committee, the approved solution will be acquired and the resources and infrastructure
required for its support will be identified and deployed.
The committee will develop and implementation plan for the migration of existing sites to the new system, including steps necessary to transition the sites' contents to standards-compliant interface designs/templates, create and integrate publishing workflows, train users and execute other essential activities.
Using the implementation plan, the committee will work closely with Academic departments and administrative units selected to be the first to migrate their existing sites to the content management solution.
During the initial implementation, the Implementation committee and adopters will collaborate to develop supporting strategies, materials, curricula, programs and processes that will be used in the broad deployment of the solution.
Phase IV: Deployment
Summer 2009
Campuswide availability
After the successful implementation, the project team will work with the Implementation committee and initial adopters to assess and
document results, refine implementation methodologies and develop a plan for campuswide deployment. The content management solution will
be offered to academic and administrative units, schools and colleges, individual departments and other administrators of official and
department UC Davis pages.