1 / 14

Technical Roles and Responsibilities

Technical Roles and Responsibilities. Keith Hazelton University of Wisconsin-Madison Ann West EDUCAUSE/Internet2. Topics. Roles and Responsibilities Conundrums. Roles: Technology Expert. Knowledgeable about the technical needs and infrastructure

nevin
Download Presentation

Technical Roles and Responsibilities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Roles and Responsibilities Keith HazeltonUniversity of Wisconsin-Madison Ann West EDUCAUSE/Internet2

  2. Topics • Roles and Responsibilities • Conundrums CAMP Directory Workshop Feb 3-6, 2004

  3. Roles: Technology Expert • Knowledgeable about the technical needs and infrastructure • Work with groups to help define technical part of requirements • Responsible for design, implementation, and operation of the infrastructure so that it meets the requirements of the campus CAMP Directory Workshop Feb 3-6, 2004

  4. Roles: Technology Advocate • Work with management on setting guiding principles • Develop standards for connecting to the directory • Work with appropriate team members to document and publish attributes and their characteristics • Act as advocate for technical architecture and why it’s a good thing CAMP Directory Workshop Feb 3-6, 2004

  5. Responsibilities: Communication and Business Plan • Translate from requirements in business terminology to technical terminology • And vice versa • Ensure accuracy and viability of communications • Participate in discussions with users and stakeholders as technical advocate for project CAMP Directory Workshop Feb 3-6, 2004

  6. Responsibilities:Design of Architecture • Campus requirements • Business needs • Applications • User environment • Support • Technology • Community requirements • Higher-education • Research CAMP Directory Workshop Feb 3-6, 2004

  7. Responsibilities:Implementation • Pre-implementation • Contribute to project plan and budget • Contribute to drivers • During implementation • Anything you do on behalf of users or their data must ultimately flow from business rules or policy • E.g. logging, populating attributes, contents of the directory CAMP Directory Workshop Feb 3-6, 2004

  8. Responsibilities:Service Operation • Ensure agreed upon operational requirements • Assist developers in using the directory appropriately • Participate as technical representative on governance bodies CAMP Directory Workshop Feb 3-6, 2004

  9. Ask Questions • Ask Why? Who? What? Where? • To be a good advocate for the architecture, you must understand the drivers (why?), requirements (what?), and environment (who and where?) • Sometimes the best solution is not the best technical solution CAMP Directory Workshop Feb 3-6, 2004

  10. Conundrums and Discussion • Some of ours • Some of yours • We’ll bring these for discussion in the the back-together session after lunch CAMP Directory Workshop Feb 3-6, 2004

  11. UWisc. System Conundrum • A major new ERP for appointments, payroll and benefits “APBS” • As a replacement SOR, upsets our IdM applecart • Since this is highly politicized, there are lots of negotiations between high level administrators (CIOs, directors, system owners) CAMP Directory Workshop Feb 3-6, 2004

  12. UWisc. System Conundrum • Since this is highly politicized, there are lots of negotiations between high level administrators (CIOs, directors, system owners) • They slip into technology solutions (data warehouses, directories,…) in the course of discussion • This will give us more of what we already have CAMP Directory Workshop Feb 3-6, 2004

  13. UWisc. System Conundrum • How do we create an opening for a fresh technological approach? CAMP Directory Workshop Feb 3-6, 2004

  14. Conundrums and Discussion • Some of yours… CAMP Directory Workshop Feb 3-6, 2004

More Related