Your SlideShare is downloading. ×
8th Annual CUNY IT Presentation "to Build a 21st Century Website for Today’s Higher Education Market"
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

8th Annual CUNY IT Presentation "to Build a 21st Century Website for Today’s Higher Education Market"

475
views

Published on

This presentation shows how Queens College completed a BHAG. Although, the website is 1.0 and much work is still needed, the college for the first time has a content management system that allows the …

This presentation shows how Queens College completed a BHAG. Although, the website is 1.0 and much work is still needed, the college for the first time has a content management system that allows the website to be updated by non-technical staff.


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
475
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 112957
  • Transcript

    • 1. Using Microsoft SharePoint
      to Build a 21st Century Website for Today’s Higher Education Market
      Naveed Husain
      Chief Information Officer
      Steven Whalen
      Director of Marketing
      Tony Ko
      SharePoint Administrator
    • 2. History of the QC Website
      • Old department sites were inconsistent in look and feel
      • 3. Centralized upkeep of website became overwhelming for a single office to manage
      • 4. QC branding needed to increase, with a focus on online presence, as more and more prospective students and parents look online for college research material
    • Building Partnerships
      • IT & Communications have to collaborate through the development of the new system that would provide the tools for creating a decentralized website with a centralized look and feel
      • 5. The project requires hiring and working with multiple vendors to design the look and feel, build the infrastructure, create content templates, and migrate content
    • SharePoint Implementation
      • What is SharePoint?
      • 6. A web-based technology platform that allows a community of end-users to easily build portals, sites, and applications that focus around collaboration, enterprise search, content management, electronic business forms, and business intelligence…(programming not required!).
    • SharePoint Implementation (continued)
      • Why SharePoint? Simplicity; Complexity; Flexibility
      • 7. Simple to use, ability to be complex, flexible to fit our needs
      • 8. Intranet/Internet – methodology to move paper process online
      • 9. Use of all media in the site (Flash, video, music, streaming, photo slideshows)
      • 10. Approval process for Internet; no approval for Intranet
      • 11. Repository of project documents
      • 12. Ongoing changes and weekly meetings between IT and Communications
    • SharePoint Implementation (continued)
      • QC SharePoint Infrastructure
    • SharePoint Implementation (continued)
      • Content Editor’s Forum
    • QC’s SharePoint Rollout
      • Vendor developed automated script for content mapping and migration
      • 13. Training classes provided for Content Editors to learn about the technology and the process for editing content
      • 14. Unique Monthly Visitors
      • 15. Legacy site: 112,957
      • 16. SharePoint site: 185,333
      • 17. Newly organized and branded website created a 64% increase in website traffic
      • 18. Release methodology (group features and functionality into major and minor versions for release)
    • Best Practices
      • Technology Best Practices
      • 19. Infrastructure
      • 20. Security
      • 21. Risk Assessment (MOSSRAP)
      • 22. Non-Technology Best Practices
      • 23. Be very clear on what you want at the beginning
      • 24. Ensure design & technology expectations are the same
      • 25. Track requests & feedbacks
      • 26. SLAs amongst departments
      DO’s
    • 27. Lessons Learned
      • Too many vendors
      • 28. Design vendor didn’t understand SharePoint
      • 29. Difficulty in procurement process
      • 30. New lexicon was not established early on
      • 31. User Acceptance Test was skipped
      • 32. Should include all content editors in UAT and feedback
      • 33. Do not forget about user and audience input
      DON’Ts
    • 34. Special Thanks
      Queens College
      • Sue Henderson -
      VP for Institutional Advancement / Executive Sponsor
      • Office of Communications
      • 35. Maria Terrone – Assistant VP for Communications
      • 36. Steven Whalen – Director of Marketing
      • 37. Adrian Partridge – Graphics Designer and Administrator
      • 38. John Cassidy – Director of Editorial Services
      • 39. Leslie Jay – Web Writer / Editor
      • 40. Office of Converging Technologies
      • 41. Naveed Husain – Chief Information Officer
      • 42. Lisa Tsay – Project Manager
      • 43. Tony Ko– Technical Project Manager
      • 44. Enterprise Application Services Group
      • 45. Network Services Group
      • 46. Training Group
      • 47. Faculty & College at large
      Vendors
    • 48. Q & A