UNC Cause 2012

14
1 A Collaborative Approach to Delivering Web Services UNC CAUSE 2012 Web.UNC

Transcript of UNC Cause 2012

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

[email protected]

Sean Semone

[email protected]

Jeff VanDrimmelen

[email protected]