Organizing Team Sharings and Tech Sharings

At the beginning of each iteration, during PLANNING, there should be a moment dedicated to reviewing the Team Sharing and Tech Sharing pages to:

• schedule the upcoming iteration’s Team Sharing

• schedule the upcoming iteration’s Tech Sharings

  • based on tickets in Ready for Development that would be great to mob

  • based on what devs expressed an interest in (check the Tech Sharings confluence page)

  • based on the findings of a spike ticket

  • based on team members attending courses

  • may be impromptu, if the opportunity arises mid-iteration

Look to record somewhere what's being shared in a Tech Sharing so that such knowledge doesn't get lost in time. Ideally, a result of a Tech Sharing should be the transcription of such knowledge into a service's Readme or Dev Handbook, lest we need to have the same Tech Sharing time and time again for newcomers

Endeavor to protect Tech Sharings from other conflicting meetings where possible. Tech Sharings may interest only a handful of people, but the rest of the team should try not to schedule something else that may be interesting to those who are on the Tech Sharing, unless reasonably unavoidable