2011

Some attendees included (apologies on name spelling)
Sara Worrell-Berg (IT Services)
Kim Seidler (IT Services)
Ken Sharp (School of Earth Sciences - Administration/Finance)
Pat Deasy (IRT Web and Systems Engineering)
David Hart (H&S Dean's Office)
Anne Pinkowski (IT Services)
Glenn Worthey (Digital Initiatives Group)
Sharon Krossa (Faculty Development and Diversity Office)
Joelle Crepsac ( Financial Management Consulting & Support Group)
Todd Ferris (IRT IT Services)
Daniel Pepke (sp?)
Glenn Peacock (IRT IT Services)

Agile Summary:
Agile Manifesto - number of team members: 5 to 9 people
Agile Methods - Extreme and Scrum are the most used methods
Test-driven development (Extreme)
Extreme - software development practices
Scrum - project management practices
3 Scrum roles: Scrum Master (process expert); Scrum Product Owner (business owner); Scrum Team Member (rest of team)
3 Scrum Meetings: JIT planning Scrum Sprint (Iteration )(1 to 2 weeks); Scrum daily meeting (Stand Up); Scrum Sprint Demo (15 minutes), then Retrospective

CAP Network project.
4 sysadmins
Lessons
1. Researchers want to collaborate with existing collaborations via CAP.
2. Law school also uses social media successfully. network for alumni + student + staff. They are looking for collaboration between schools.
3. Determining what the best user authentication modules to support.
4. How do you quantify the success and viability of activating the social networks?
5. Enforcement is a challenge in regards to people who have left the university.
6. Stanford owns all data.

Session was about IT leadership at Stanford (or lack thereof).
Question was posed "What should lT leadership look like?" at Stanford.
Responses took the direction around not so much what IT Leadership should look like, but what obstacles were in the way to prevent effective leadership.
- Management and leadership are not the same. Leaders are those that create vision, managers are those that implement and bring the vision to fruition.
- Communication between the IT Leader community at Stanford is not effective or in some cases, just not there.

Note this is a just a quick capture doing the best I can. Email me if you have updates to these notes ... tec@stanford.edu
Areas represented:
Student Affairs
Earth Sciences
Dinning Services
VPUE
Networking
Archivest
Documentation
Engineering
ITS
GSB
Humanities
Academic Computing
School of Engineering
How to reach students is important since almost all have a mobile device of some sort. Meal plans would be a good fit.

10 attendees
Responsibility for accessibility does not end at Stanford boundaries
4 essential types of disabilities (re: web accessibility)
-Vision impairments
-Auditory impairment
-Mobility impairment
-Cognitive disabilities
Goal: try to identify issues for those types of disabilities, and develop ways to address them.
As a campus, we need to own this problem collectively. Should develop a proactive approach to online accessibility.