CMSE 495
Michigan State University Data Science Capstone.
In-Class Assignment: First Team Meetings
Throughout the semester you will be expected to conduct regular team meetings (weekly). For every team meeting you will identify a facilitator, time keeper and note taker (rotate these roles).
Your instructors will expect to be able to go to your team drives at any time during the semester and be able to review your up-to-date meeting notes. If they are not there your entire team will receive a zero and will not be able to make it up.
Today we will be practicing for the first official meeting. To help you out we have provided a draft agenda:
Meeting Agenda
- (5 minutes) Identify and record meeting roles (Note taker, Timekeeper, Facilitator).
- (5 minutes) Review this agenda (make changes as needed).
- (10 minutes) Create and share team git repository. (ensure your instructors are able to clone).
- (10 minutes) Review Milestone Assignments, finish up team charter and hand out “Next Actions” to everyone on the team. Next Actions should be clearly recorded in your meeting notes with who what and when information.
Understanding Git
It is assumed that you have been introduced to git in previous classes. We will be using it a lot in this class. Students that are uncomfortable with git may want to review the following tutorials. It is the entire teams responsibility to help your fellow members learn and use git properly:
Another fun resource is the following game which tries to teach you git:
Getting Credit for this assignment
To get credit for this assignment submit your meeting notes to your teams drive. More information can be found here. Before you leave you must make sure that everyone on the team (including the instructors) are able to clone your repository.
Rubric: First Team Meeting & Git Setup Assignment
| Criteria | Excellent (Full Credit) | Satisfactory (Partial Credit) | Needs Improvement (No Credit) | Points |
|---|---|---|---|---|
| Meeting Agenda Coverage | All agenda items were clearly discussed and documented. Notes reflect thoughtful discussion and planning. | Most agenda items were addressed, but some details are missing or unclear. | Few or no agenda items were addressed. Notes are vague or incomplete. | 5 |
| Team Collaboration | Notes reflect active participation from all team members. Roles and responsibilities are clearly assigned. | Some team members participated. Roles are mentioned but not clearly defined. | Little evidence of collaboration. Roles are missing or unclear. | 5 |
| Git Repository Setup | Repository is properly initialized. All team members and instructors have access and can clone it. | Repository is set up, but access is incomplete or not verified for all members/instructors. | Repository is missing or inaccessible. | 5 |
| Clarity & Organization of Notes | Notes are well-organized, easy to read, and free of grammar/spelling issues. | Notes are somewhat organized but may contain minor errors or unclear sections. | Notes are disorganized, hard to follow, or poorly written. | 5 |
| Submission & Accessibility | Notes are submitted to the team drive on time and accessible to all team members and instructors. | Notes are submitted but access is limited or submission is late. | Notes are not submitted or not accessible. | 5 |
| Total | 25 points |
Written by Dr. Dirk Colbry, Michigan State University
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.