waterloo cms project · 2011-08-15 · 1. ease of maintenance (content contributors, website...
TRANSCRIPT
Waterloo CMS Project
New project directionProject team overview
k dMajor work underway
Change in direction
l il b iDrupal pilot website
Change officialFeb 10 2010Project Charter (http://ist.uwaterloo.ca/projects/wcmsproject/waterloo‐cms‐project‐charter‐20100210.pdf)
Ease of maintenance (content contributors website 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators)
2. Responsiveness to changes in University’s business environment (e.g. look and feel)
3. Distributed web‐content management
4. Responsiveness to changing technology environments & requirements (e g social collaboration & social requirements (e.g. social collaboration & social networking)
5. Enhanced and extended functionality (e.g. modules/plug‐5 f y ( g /p gins)
Team membersTeam structure (organizational chart)
University‐wide participation17 core project team members
l h13 consultants to the project
AHS Arts CS Engineering Environmentg gCPA CEL (DCE) Housing HR IST Library OPD Registrar’s Secretariatg
web.uwaterloo.caweb.uwaterloo.ca
Project SponsorProject Sponsor
Project Management Sub‐TeamSub‐Team
Accessibility Application Architecture Communications ccess b tySub‐Team
Application Architecture Sub‐Team
System Architecture Training & Support W b D i I l t ti
Co u cat o sSub‐Team
System Architecture Sub‐Team
Training & Support Sub‐Team
Web Design Implementation Sub‐Team
Accessibilit compliance1. Accessibility compliance2. Team training3 Sandbox (test sites)3. Sandbox (test sites)4. Training resources5. Content migration strategy6. Pilot website7. Requirements definition
A li i hi8. Application architecture9. Web Redesign Project collaboration10 Project management10. Project management
Legislative requirementsWeb content accessibility (WCAG 2.o – Level A)User interface accessibility (ATAG 2.0)
Application architecture/configurationModules (text editor)Content types (form entry)
February 2010 – “Drupal Essential Training”
dLynda.com courseWatch DVD as teamUse sandbox to work on exercises individually
Lynda.com informationOnline courses DVDs
Drupal sandbox – February 2010
fResources for project and university‐wide
h l blResearching available resourcesListing useful resourcesb b kObtaining resources (DVDs, books, etc.)
Creating documentation (research phase)lPreparing training courses (content analysis)
SEW Course: Preparing Your Web ContentContent analysis (audit/inventory)
b h l d b dFebruary, March, April 2010 and beyondTool available for University use – end of Feb
SEW information website h l ff h lhttp://ist.uwaterloo.ca/cs/stafftraining.html
UWaterloo Web Resources websiteCentral location housing/linking to web resourcesC t t d t J Content needs assessments – Jan 2010Findings from needs assessments transcribed
Part ofCMS training plan & strategy (resources)CMS training plan & strategy (resources)CMS adoption plan &strategy (adoption kit)
RequirementsBased on previous CMS projectDocumented (captured in spreadsheet)Weighted (priority)Being reviewed by project team (common vision)Inform application architectureppInform testing
Research phaseModules Naming conventionsTaxonomyCommunications with other universitiesConsulting services (implementation & support)g p pp
CollaborationRegular meetings & communications
ll h d lCMS rollout with design templatesDeliverables for CMS implementation
Project managementProject Charter updateProject Management Plan▪ Work Breakdown Structure (WBS) revision▪ Schedule review & adjustments
University communications▪ web.uwaterloo.ca▪ Presentations/meetings▪ UW web mailing list▪ UW web mailing list
???