2017

This session is a workshop to gather and share ideas on where, why, and how to gather student feedback for our various projects.

Mike and Sherwin, VPTL Student Technology 

Thanks for coming
You’re already in groups
This session is a group discussion

The prompts…
 

• What do you do currently to gather or utilize student feedback?
• What type of feedback would be useful?
• How could we gather feedback?

We broke into four groups to discuss these issues and find ways to address these issues. This is representative of what we do in the UXers CoP every Friday at 1 pm in the VPTL building on Panama. Ux.stanford.edu. 

We also tried to identify groups or resources on campus to help. 

Faculty teach different styles, so technology has to adapt..

- Question about hardware and TTL - what are the most positively received technologies?

writing surfaces go a long way.... whiteboards, tablets? How much technology

- anything more than whiteboards can be too much and has marginal value

- Captivo - mounts above whiteboard and captures writing, creates slideshow of "pages", incremental PDF. No logins, no account. Limit to 6' whiteboard currently. Inexpensive ($500). 

Flexibility more important than tech

• https://summerinstitutes.stanford.edu/

  • Initial Pain points: Initial content authors were not able to login. All content edits had to go through one person

  • Video uploading was difficult but now you can use Youtube URL

  • “Paragraphs” help with controlled output of text and design

Session began with introduction and context.  Participants represented  SLAC, SUL, GSB, FMS, UIT, H&S and other groups.   There is growing interest in the Data Practitioners CoP with about 20 Schools/Departments participating.  Cop  has been instrumental for knowledge sharing, getting help , and exposing new data sources.   Question posed to the group about their areas of interest, which included: 

Contact:
Feel free to contact me with questions. Or better yet, ask on the Slack channel below! I'll be listening there.
Email: nicholjf@stanford.edu

Links:
Slack channel: https://stanfordcop.slack.com/messages/C8831M9SN/">https://stanfordcop.slack.com/messages/C8831M9SN/
Google Slides presentation: https://goo.gl/LH8L6J

DevOps Best Practices - a call to action
 
CIO Working Group formed to explore DevOps on Campus
Some folks believe they already do DevOps.
State of DevOps at Stanford
 
Desire for a standard definition of DevOps across campus.
We looked at the Wikipedia definition.
Benefits of DevOps - why do this thing?
Biz & Academic Continuity
Infrastructure As Code; Repeatability and Predictability.
Accountability & Supportability; shared responsibility
Security...bake it in to the product lifecycle 

Notes from 9:15am Minhtu Earl session – topic is “New Ideas”

Minhtu introduces by saying she doesn’t have slides or any agenda, just wants to trade ideas

Sherry talks about how many instant messaging and how many platforms all need her attention, inability to get reports into some of the platforms, how the architecture drives some reporting, like ServiceNow is kinda similar to Salesforce which means UIT needs to support several platforms