Changes between Version 12 and Version 13 of org/meetings/TorMeetingTemplates


Ignore:
Timestamp:
Sep 14, 2017, 10:51:45 PM (21 months ago)
Author:
mikeperry
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/TorMeetingTemplates

    v12 v13  
    77This page serves to provide meeting templates primarily for the team meetings, with some overlap for community meetings. It is intended to describe the types of meetings all teams should have, as well as additional meetings that individual teams tend to have.
    88
    9 Every meeting has three components: Goals, Outputs, and Stakeholders. Meetings can also have additional explicit non-goals, and may also list Bottlenecks -- people who need to be there, but tend to be in high demand for other concurrent meetings.
     9Every meeting has at least three components: Goals, Outputs, and Stakeholders. Meetings can also have additional explicit non-goals, and may also list Bottlenecks -- people who need to be there, but tend to be in high demand for other concurrent meetings.
    1010
    11 When creating a schedule using these templates, one should be sure to transfer the Duration, Stakeholders, and Bottleneck fields to the schedule, to ensure proper scheduling. The Stakeholders field in particular should help determine if this is a team meeting, or if it should be held on one of the community days.
     11When creating a schedule using these templates, be sure to write down specifics for these fields for your meeting in the schedule. In particular, the Duration, Stakeholders, and Bottleneck fields are essential to ensure proper scheduling. The Stakeholders field will help determine if this is a team meeting, or if it should be held on one of the community days.
    1212
    1313= Meeting Templates =
     
    1717|| Duration || 20 minutes, 60 minutes, 90 minutes ||
    1818|| Description || What is this meeting about? How does it usually run? ||
    19 || Goal || Describe the meeting's goal ||
     19|| Goal || Describe the meeting's goal. Goals should be substantive and ideally also measurable, so we can ensure meeting time is well spent. ||
    2020|| Non-Goals || Describe ways this meeting type can get derailed or distracted by off-topic material (optional) ||
    2121|| Outputs || What notes/diagrams/documents/tickets should the meeting produce? ||
    22 || Stakeholders || Who should attend for the meeting to reach a conclusion? ||
     22|| Stakeholders || Who has to attend the meeting in order for it to reach its goals? ||
    2323|| Bottlenecks || Who do we need to attend for a decision to be made, but is at risk of having a conflict? (optional) ||
    2424
     
    2929|| Duration || 60 minutes ||
    3030|| Description || Plan and document what the team wants to accomplish in the next 6 months. For development-oriented teams, this is the creation of milestones and a schedule. For non-development teams (and Agile teams), this is a story or narrative (or set of narratives) of what Tor should look like in 6 months as a result of your work. ||
    31 || Goal || Produce some kind of plan for the next 6 months, with specific people committing to roles and/or specific action items. ||
     31|| Goal || Produce a plan for the next 6 months, with specific people committing to roles and/or specific action items. ||
    3232|| Outputs || For development teams, this is usually a schedule of post-it notes that gets transferred to the wiki and trac tags, usually with difficulty estimates and people+sponsor tags. For non-development or agile teams, this can be a written narrative of a plan, with specific action items and/or roles needed to achieve that plan. ||
    3333|| Stakeholders || Team members ||
    3434|| Bottlenecks || Isabela ||
    35 
    3635
    3736=== Team Retrospective ===