2 PM ET / 1 PM CT, March 24, 2014

Attendees

Notetaker: TBD

Staff transitions upcoming
Review Expectations for Tech lead and QA Lead (15 minutes)
1. Reconfirming the roles of tech lead and QA lead - they are advanced team members available to the team with specific expertise; working with the POs on any planning and priority-setting. Don't need to set out a specific process for POs and tech lead to communicate with each other, just be clear that it should happen.
2. Claire and Rick will revise the scrum master, tech lead and QA lead descriptions on the wiki and run them by the PDs
Review focus for July release (similar to high level focus paragraph Julie requested for the April release) (20 minutes)
1. attached again is the agreed upon statement for April and the draft up for discussion for July: https://docs.google.com/a/nd.edu/document/d/1Zl9_vpN5BqGcdBGwn5vM6vskgXmO7DY_uNVgFOBhyDQ/edit
2. (notes from 3/24/2014 PD discussion and thoughts about the draft are captured in the Google doc linked above)
Review process for on boarding new developers (partner institution contributor vs. non-partner contributor) (5 minutes)
1. Confirmed we would like to have new team members from partner institutions have some conversation with lead PO (re: process) and tech lead (re: code familiarity, how to come up to speed) as they join the project. This should be more lightweight than the onboarding for non-partner team members. Claire will revise wiki pages that address this.

The items below will be rolled over to the next PD meeting

Review work and resource commitment patterns (i.e. 25% resource on 1 sprint vs. 100% on 1 out of 4 sprints) (10 minutes)
Suggest dates for face to face project meeting (5 minutes)