ScrumU Small Group May 7 2010

Attendees: GA Tech (Lori), Wake Forest (Steve), ND(Tracy), MN SCU

Tentatively planning next large group meeting for June 18. Lori will confirm. This will be a speaker on the topic Agile Artifacts.

GA Tech: Parent portal went live, but there have been a number of post-production changes. Looking forward to lessons learned on this one. Starting procurement project, implementing 3rd party software where company uses agile approach. Will be bringing over functional leads to scrum room.

ND: Struggling with one project where vendors working in waterfall approach, and scrum team couldn't meet sprint goals because vendors deliverables were late. Talked about how we might do this differently - could we change contract language that would meet general counsel requirements, but leave room for more agility. Also could include agility as a focus in vendor selection process. Current scrum teams are all large project efforts. We're in the next few weeks piloting a cell team to focus on smaller lower risk projects, allowing team to focus on smaller projects, and have transferred support responsibilties to other people.

Wake: Live with Banner 8 upgrade scrum project, had banner consultant on site for assistance with issues, but there weren't many. Very smooth go live. Started new scrum - using Google docs to make Scrum board, artifacts visible. Working with test team and prod support team to determine what content is needed for agile specs. Working with project managers to figure out how can plan sprints considering a number of projects, fixes, etc., prioritized, figuring out how that can be incorporated into planning mtgs.

MN SCU: Still working on selecting a scrum coach. Dealing with impacts of reduced staffing, decided to defer some maintenance efforts and focus on completing one project at a time. Figuring out how to manage testing in an agile environment. Have a QA team, less than 2 years old, typically assigned to high profile projects. Talked about how to incorporate requirements gathering - during sprint, or before. MN prefers to do before. On larger projects, Wake is thinking about making a story during sprint. ND has an overarching story, and then chunks into business functions where tasks fall into varous sprints.

Proposed future topic: Developing release plans