Attendees

• A. Soroka
• Andrew Woods
• Unknown User (escowles@ucsd.edu)
• Eric James
• David Wilcox

General

• Indicates who took minutes - 
• Google-hangout at: 
  
  • https://plus.google.com/hangouts/_/event/c1glu6soq43r1rr6ou17qtobug8

Agenda

1. Meta analysis of sprint process
2. Summarize final state
3. Walk through in-process and unstarted tickets
4. Teeing up for next sprint

Minutes

Reflection

Esme

1. Small group
2. Productive and smooth
3. Beginning of sprint, team did not know what the sprint would involve
   • It took two days to determine the implication of use case analysis
   • If we could do it again...
     • Do analysis at the end of previous sprint

Adam

1. Been out of action, computer issues
2. Noting the fragility of running on limited developer pool
3. Productive in terms of generating conversation around content modeling
   • Having community conversation should happen before driving too deep
4. Need to surface conversations and engage input from non-dev community
5. Esme: site visits are constructive for input (WGBH/BPL)
   • Virtual or otherwise, site visits with orgs using Fedora could be good
   • User testing could include virtual focus groups

Tickets

1. Current and Backlog tickets were reviewed and re-sorted.

Actions