commit 2bc6750540095c3c3563265f1d1d60719ed34c4b Author: Mark Claypool <claypool@cs.wpi.edu> Date: Tue Aug 23 09:35:10 2022 -0400 Updates diff --git a/meetings.md b/meetings.md index 2fb14a0..a63460a 100644 --- a/meetings.md +++ b/meetings.md @@ -19,6 +19,7 @@ Everyone on the team should meet to prepare the agenda. A bulleted list is fine. Typical agenda items include: + - Summary of accomplishments the previous week - Discussion items - Summary of plans for subsequent week commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Aug 8 13:58:58 2022 -0400 Updates diff --git a/meetings.md b/meetings.md index 68b7849..2fb14a0 100644 --- a/meetings.md +++ b/meetings.md @@ -1,6 +1,9 @@ -# Running a Meeting +--- +pagetitle: Running a Meeting +version: 1.2 +--- -v1.1 +# Running a Meeting Learning how to run a professional meeting is a skill. Students will learn and apply this skill to each meeting with the faculty advisor commit 385f82b8934327afa719a97fb9e7900893906afc Author: Mark Claypool <claypool@cs.wpi.edu> Date: Wed Sep 25 14:28:05 2019 -0400 Updates diff --git a/meetings.md b/meetings.md index ea3f96b..68b7849 100644 --- a/meetings.md +++ b/meetings.md @@ -1,5 +1,6 @@ # Running a Meeting -v1.0 + +v1.1 Learning how to run a professional meeting is a skill. Students will learn and apply this skill to each meeting with the faculty advisor @@ -22,7 +23,6 @@ Typical agenda items include: *Tip*: assign a name next to each agenda item. This is the person that is responsible for leading the discussion about that item. - ## Roles Every meeting will have a leader and a note-taker. @@ -46,7 +46,7 @@ chance to be leader and scribe. The outcome of the meeting is in the form of notes, taken by the scribe. Detailed minutes recording exactly what is said are not required, but instead, notes should capture important -issues/questions/conclusions. +issues/questions/conclusions. The scribe should share notes with the student team after the meeting, revising based on team feedback. The suggestion is for the student @@ -54,3 +54,8 @@ team to explicitly discuss the notes at their next meeting. When the team has agreed upon the notes, the scribe should archive the notes in a repository shared by the team (e.g., Google docs). + +## Action Items + +Make sure to end the meeting with a wrap-up of the action items - what +is to happen next, tasks, who is doing what, etc. commit c97ff59acd7ebe95708b2c988909b289356b55b3 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Sat Feb 3 07:29:31 2018 -0500 Updates diff --git a/meetings.md b/meetings.md index 0310117..ea3f96b 100644 --- a/meetings.md +++ b/meetings.md @@ -1,4 +1,5 @@ # Running a Meeting +v1.0 Learning how to run a professional meeting is a skill. Students will learn and apply this skill to each meeting with the faculty advisor commit 5957c91b3ee609fa36016ada2e21ebd7d3ff50f8 Author: Mark Claypool <claypool@cs.wpi.edu> Date: Mon Nov 27 15:00:33 2017 -0500 Initial versions diff --git a/meetings.md b/meetings.md new file mode 100644 index 0000000..0310117 --- /dev/null +++ b/meetings.md @@ -0,0 +1,55 @@ +# Running a Meeting + +Learning how to run a professional meeting is a skill. Students will +learn and apply this skill to each meeting with the faculty advisor +(and mentor, for sponsored projects). + +## Agenda + +The agenda provides a "roadmap" for the topics that are to be +discussed at the meeting. + +Everyone on the team should meet to prepare the agenda. + +A bulleted list is fine. + +Typical agenda items include: +- Summary of accomplishments the previous week +- Discussion items +- Summary of plans for subsequent week + +*Tip*: assign a name next to each agenda item. This is the person that +is responsible for leading the discussion about that item. + + +## Roles + +Every meeting will have a leader and a note-taker. + +**Leader** - The leader is responsible for working through the agenda. +While conversation can go to topics not on the agenda, the leader +should make sure the meeting focus gets back to any items that are +important in the allotted time (usually 30 or 60 minutes). + +**Scribe** - The scribe is responsible for taking notes during the +meeting. + +Everyone in the group should talk, not just the leader. + +The roles can be fixed for the duration of the term/project, but early +on, students should rotate through the roles so that everyone has a +chance to be leader and scribe. + +## Notes + +The outcome of the meeting is in the form of notes, taken by the +scribe. Detailed minutes recording exactly what is said are not +required, but instead, notes should capture important +issues/questions/conclusions. + +The scribe should share notes with the student team after the meeting, +revising based on team feedback. The suggestion is for the student +team to explicitly discuss the notes at their next meeting. + +When the team has agreed upon the notes, the scribe should archive the +notes in a repository shared by the team (e.g., Google docs).