...
Delphine uses agile/scrum at Penn State - calls some members of her team "ingesters"
NCSU - refer to powerpoint for books to read
resources:
blog.mountaingoatssoftware.com
Books: http://library.mit.edu/item/001270790
http://library.books24x7.com.libproxy.mit.edu/toc.asp?site=bbbga&bookid=8392
notes from Emily's presentation:
Product backlog is supposed to be prioritized. But library staff have a difficult time prioritizing issues against each other. They work best talking generally about what they think should be part of a given iteration. Then we negotiate with them about what we think we can accomplish. The IT product manager plays a large role in determining final priorities here.
Testing – “the weakest link”. For smaller projects w/o massive codebase, when is it faster and better to automate testing? No QA experts, so try to utilize product teams with regular updates throughout the cycle. In the end, developers and IT product managers have to do first pass at QA testing. Have not done a good job defining acceptance tests for each piece of functionality.
Our group is responsible both for real-time support and development. How to handle? Working toward documenting time spent on real-time support emergencies in JIRA and track how much effort spent on that vs. development. This feeds our estimation of how many hours are available for each person for each cycle; assume some time goes to support.
Greenhopper & JIRA
Google docs & JIRA