| Time | Item | Who | Notes |
|---|
| 2 minutes | Some crazy question just for fun | | worst flights... |
| 10 minutes | Review the lead-up to fall term - what went well, what could have been better | All | - Primo any new updates - draft an expectations document
- spelling out communication method (frequency and type)
- defining what will change and what won't change
- lay out known issues
- codify a group of people who will be responsible for testing and feedback
- sils group - feedback goes to group
- Product Owner for PRIMO
- Dan would be Technical Lead
- Basic Primo issues came up in conjunction with the new UI issues
- communications went well
- sessions were a good and positive thing
- getting stakeholders on board was very difficult
- A/B testing
- SA /Hyrax - has a testing group that could be a good model
- ++Work plan and Gant chart are good for visual check in.
- ++Weekly retrospectives are good
- LibCal needs to be pushed forward
- ++Springshare has added HTTPS and changed front end
- Could be outages (we've had 3 of them recently)
- TRESbien & Beaver Tracks projects stretched developers thin this summer.
- Setting criteria for projects we take on – this is something to bring forward to a retreat
- How long will the application be live?
- Project selection for students
- Be realistic about what to expect from students and how much time we have to give to them to develop them.
- Establishing expectations and standards for ourselves and our projects
- More time spent researching problems when projects are proposed
- ++Open Hours
- twice a month
- alternate with ETS department meetings
|
| | Demo of a potential system for submitting problem tickets | Josh | Send the link to the form out and have people test. |
| | Quick review of Docusign workflow and travel requests | Margaret | |
| | If time, chat about retreat possibilities | | Go to Guin for retreat |