Speaker: Galadriel Chilton, University of Connecticut
Used SCRUM for assessment project for their electronic resources collection. They wanted to make sure that all library staff in collection development would be able to manage annual reviews of eresources.
SCRUM: A breathtakingly brief and agile introduction by Chris Sims & Hillary Louise Johnson
First you put together a team, then you create the stories you want to build from the deliverables. Once you have your story, you have a sprint planning meeting for the following 2 week period, and this will take about 4 hours. This planning takes the deliverables and the story, and then develops the tasks needed to accomplish this. You’ll also need to factor in available time because the daily work still needs to be done. Each task will get an estimated time (determined by consensus). Tasks are assigned based on availability and skill set.
The sprint story board is a physical item. You document the story, then three columns of not started, in progress, and done. Each day of the sprint you have a check-in to report on the previous day’s work, problems, and the work that will be done that day.
One of the down sides is that they are a small team, and by the second or third sprint, they were getting exhausted by it. They had other jobs that needed to be done during this as well.
It worked really well for balancing the work against the other tasks of each person, and avoid burnout or a sense of imbalance.
Q: What other projects would be useful for this method?
A: Moving proxy services; mass communication with vendors to update mailing address and contacts; tracking time and deliverables for annual reporting; projects you don’t know what you have to do ahead of time.
Tracking time: Chrome plugin, post-it notes; spreadsheet of a time managed by a time-tracker
Q: minimum number of people? 4
