際際滷

際際滷Share a Scribd company logo

UNC Cause 2012

Download as PPTX, PDF
Billy Hylton
Billy Hylton

This document proposes a collaborative approach between the OASIS Web Services team and the ITS Web Services team at UNC-Chapel Hill to deliver web services. It notes the current inefficient model with different technologies, duplication of efforts, and lack of standards. The proposal is for the two teams to unite and work together, which would build knowledge through cross-disciplinary sharing, increase efficiencies and reduce costs, meet a wider range of needs, and future-proof their services. Working together as a unified team would scale to allow new services and benefit the university community.

1 of 14
Download to read offline
1 A Collaborative Approach to Delivering Web Services UNC CAUSE 2012 Web.UNC
2 Snapshot OASIS Web Services College of Arts & Sciences Content management web solutions to departments, centers, and programs Free of charge to College 70+ departments ITS Web Services Office of CIO, ITS Web design, development, and content management services for ITS, campus units Cost recovery model Serve internal and external customers
3 Issue: An Inefficient Model Landscape Different technologies Duplication of efforts Lack of standards, policies, processes Resource constraints Customer confusion Inconsistent UX and branding
4 Create, administer, and support a truly collaborative approach to delivering web-based services to UNC- Chapel Hill and beyond. Proposal
5 OASIS & ITS Web Teams Unite First Step: A Partnership
6 Model Model will scale to allow new services
7 Model Model will scale to allow new services
8 Model Model will scale to allow new services
9 Building Community
10 Benefits Building knowledge via cross- disciplinary skills, insights, and perspectives Communications (i.e Alert Carolina messaging) Standards Design and branding consistencies (set of WP themes for different use cases) Increased efficiencies, reduced costs Meeting wider range of needs Scalable infrastructure Security (i.e plugin and theme review process) Future-proofing If you want to go fast, go alone. If you want to go far, go together.
11 Lessons Learned Learning Importance of governance (but need to be flexible) Different cost models (may be confusing) Demonstrate value (metrics, feedback) Importance of integrated project management Communication (service changes, maintenance, procedures, etc.) Risks of tool sprawl
12 Next Steps Continue to evolve model, governance, technical framework, partnerships Grow and respond to community content editors, communicators, developers, and units Mobile UNC System/Higher Ed outreach Collaboration opportunities with you? How might this model apply to different service offerings beyond web and UNC-CH?
13 Questions
Thank You Billy Hylton billy_hylton@unc.edu Sean Semone semone@unc.edu Jeff VanDrimmelen jeffvand@unc.edu

More Related Content

UNC Cause 2012

  • 1. 1 A Collaborative Approach to Delivering Web Services UNC CAUSE 2012 Web.UNC
  • 2. 2 Snapshot OASIS Web Services College of Arts & Sciences Content management web solutions to departments, centers, and programs Free of charge to College 70+ departments ITS Web Services Office of CIO, ITS Web design, development, and content management services for ITS, campus units Cost recovery model Serve internal and external customers
  • 3. 3 Issue: An Inefficient Model Landscape Different technologies Duplication of efforts Lack of standards, policies, processes Resource constraints Customer confusion Inconsistent UX and branding
  • 4. 4 Create, administer, and support a truly collaborative approach to delivering web-based services to UNC- Chapel Hill and beyond. Proposal
  • 5. 5 OASIS & ITS Web Teams Unite First Step: A Partnership
  • 6. 6 Model Model will scale to allow new services
  • 7. 7 Model Model will scale to allow new services
  • 8. 8 Model Model will scale to allow new services
  • 10. 10 Benefits Building knowledge via cross- disciplinary skills, insights, and perspectives Communications (i.e Alert Carolina messaging) Standards Design and branding consistencies (set of WP themes for different use cases) Increased efficiencies, reduced costs Meeting wider range of needs Scalable infrastructure Security (i.e plugin and theme review process) Future-proofing If you want to go fast, go alone. If you want to go far, go together.
  • 11. 11 Lessons Learned Learning Importance of governance (but need to be flexible) Different cost models (may be confusing) Demonstrate value (metrics, feedback) Importance of integrated project management Communication (service changes, maintenance, procedures, etc.) Risks of tool sprawl
  • 12. 12 Next Steps Continue to evolve model, governance, technical framework, partnerships Grow and respond to community content editors, communicators, developers, and units Mobile UNC System/Higher Ed outreach Collaboration opportunities with you? How might this model apply to different service offerings beyond web and UNC-CH?
  • 14. Thank You Billy Hylton billy_hylton@unc.edu Sean Semone semone@unc.edu Jeff VanDrimmelen jeffvand@unc.edu

Editor's Notes

  • #3: Sean, billy, jeff
  • #4: ** BILLY*** Show of handsSummarize CMS landscape at that timeDuplication of resources(themes, resources, widgets) Art Department story
  • #5: ** BILLY **March, 2011 ProposalAgreed on one CMS Chose WordPress based on success of web.unc.eduDiscussed model How to meet a very wide range of needs in a scalable model
  • #6: ** Billy **Staff split between both teams (MOUs, technically ITS staff administrative standpoint Supporting each others customers
  • #7: Jeff
  • #8: Jeff
  • #9: Jeff
  • #10: JeffBE SURE MENTION STUDENT WORKERS
  • #11: Sean
  • #12: Sean