Jump to: navigation, search


General stats

  • About 10-30 people attend.
  • Only a handful of groups tend to hold them; for this cycle we're seeing some teams choose not to.
  • Often subteams form around a specific tasks to complete.
  • Meeting space is donated by companies.
  • Travel costs are the responsibility of the individual attending (their employer most likely).
  • Sometimes companies will host meals (not often).


  • Choose the Design Summit first for gathering the whole team for decisions and roadmap alignment.
  • Attend or host in the early days of team-forming.
  • Plan for real work getting done and a specific outcome in mind.
  • Add your sprint to the Sprints wiki page.
  • PTL or a designated delegate typically organizes the event.
  • You can co-host sprints across teams. However, productivity also lies in the small, quiet environment, and social bonding is easier in smaller groups.
  • Favor separate sprints unless there are good cross-pollination opportunities between co-hosted teams.


  • Pitfall can be a feeling of "required" attendance (social or actual) causing hard feelings; also some types of contributors will be marginalized despite best efforts, such as those without a corporate sponsor, family caretakers, and people who need Visas to travel.
  • Often there's a choice implied in choosing what an individual travels to; adding a midcycle sprint means a choice has to be made.
  • Virtual aspects of a midcycle require additional support such as open source tooling, or if using non-open source tooling, you must get agreement from participants.