waterloo cms project · 2011-08-15 · 1. ease of maintenance (content contributors, website...

19
Waterloo CMS Project

Upload: others

Post on 14-Jul-2020

1 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

Waterloo CMS Project

Page 2: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

New project directionProject team overview

k dMajor work underway

Page 3: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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)

Page 4: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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)

Page 5: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

Team membersTeam structure (organizational chart)

Page 6: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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

Page 7: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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

Page 8: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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

Page 9: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

Legislative requirementsWeb content accessibility (WCAG 2.o – Level A)User interface accessibility (ATAG 2.0)

Application architecture/configurationModules (text editor)Content types (form entry)

Page 10: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

February 2010 – “Drupal Essential Training”

dLynda.com courseWatch DVD as teamUse sandbox to work on exercises individually

Lynda.com informationOnline courses  DVDs

Page 11: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

Drupal sandbox – February 2010

Page 12: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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)

Page 13: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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

Page 14: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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)

Page 15: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

RequirementsBased on previous CMS projectDocumented (captured in spreadsheet)Weighted (priority)Being reviewed by project team (common vision)Inform application architectureppInform testing

Page 16: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

Research phaseModules Naming conventionsTaxonomyCommunications with other universitiesConsulting services (implementation & support)g p pp

Page 17: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

CollaborationRegular meetings & communications

ll h d lCMS rollout with design templatesDeliverables for CMS implementation

Page 18: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

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

Page 19: Waterloo CMS Project · 2011-08-15 · 1. Ease of maintenance (content contributors, website administrators, website designers, web developers, system administrators) 2. Responsiveness

???