Meetings/WMF team updates/

Goals

 * Increased visibility into what specifically teams are doing day-to-day, which will
 * Quickly surface overlap with other teams, facilitating better inter-team collaboration
 * Quickly highlight where we can better support one another
 * Heighten visibility into the commitments we make to one another and (hopefully friendly) peer pressure to follow through
 * Overall improvements in the individual projects teams are working on (and ultimately in the overall experience of our users)
 * Surface blockers, impediments, and OMFG-what-you're-about-to-do-will-take-down-the-site moments earlier and faster, generally increasing throughput and quality
 * Other areas in which we can/need to improve inter-team communication/collaboration/planning/etc will become quickly apparent through both the value added of the SoS as well as its limitations

Details

 * Frequency of once per week
 * One technical rep from each team that wants to participate (rep can rotate)
 * 30 minute timebox (we originally talked about 60, but it was impossible to schedule a 60 minute block to accommodate participating teams' schedules. If 30 mins doesn't work, we can adjust)
 * The following questions are addressed by each team rep:
 * What has your team done since we last met?
 * What will your team do before we meet again?
 * Is anything slowing your team down or getting in their way?
 * Are you about to put something in another team’s way?
 * Any conversation out of scope is handled appropriately by facilitator
 * Notes should be taken and archived
 * It is the responsibility of the team rep to disseminate appropriate information to their team/ensure commitments made during SoS are fulfilled
 * Keep the meeting open to chickens, but only allow them to actively participate in the conversation as needed
 * We'll retrospect after a month to assess the utility of this and see where we can make improvements

[ Content from Arthur's emails to teampractices ]

Meeting Notes
2013-10-15