Team Charter

Before we started working to select a problem, we decided as a team that it was important to have the same set of expectations for each other as a group moving forward – our Team Charter addresses this concern. This Charter was devised and agreed upon by all of us as a group, and covers the main aspects that we felt we needed to be on the same page for: our overall goals for the project, our expectations for what each member should individually contribute, the procedures we use to achieve said goals and meet said expectations, and the consequences for not following those procedures.

 

Team EULER Charter Revised 10/13

GOALS: What are our team goals for this project? What do we want to accomplish? What skills do we want to develop or refine?

Our top 5 goals in order of importance are:

  1. We want to be proud of the outcomes of the project (e.g., highlight the project in a job interview)
  2. We want to have a functional prototype by the end of the project.
  3. We want to create a work environment where each member is heard, valued,  and appreciated
  4. We want to create a solution that is unique, creative, and hasn’t been thought of before.
  5. We want to learn new topics/concepts through this project.

EXPECTATIONS: What do we expect of one another in regard to attendance at meetings, participation, frequency of communication, the quality of work, etc.?

  • Attendance is expected; however, communication is necessary
  • If you are worried about having a contagious disease, join the meeting via zoom.
  • React to slack messages to make it known that you have seen it.
  • Try to take constructive criticism professionally, not personally. 

POLICIES & PROCEDURES: What rules can we agree on to help us meet our goals and expectations? 

  • Aim for transparency in communication (e.g., if you disagree with something someone has said).
  • Notify Professor Utter and team members if you’re going to miss a deadline in a timely manner.
  • Use shared google drive for anything related to ME 497/8.
  • If you miss a meeting, it’s your responsibility to:
    • Let the whole team know
    • Check the meeting minutes for what we did at the meeting you missed (look for action items, and mentions of new documents/files)
    • Talk to team members to get updated on how the meeting went
    • Make your contributions to what we worked on as you would have if you were able to make it
      • Missing a meeting doesn’t mean you’re off the hook for a deadline.
    • Find out from the Task Manager what the expectations are for the next meeting
  • Along the lines of disagreements regarding design choices or the problem scope
    • Have a team debate in an allotted time frame to determine a majority decision
    • Allow stakeholders to determine decisions based on their specifications

CONSEQUENCES: How will we address non-performance in regard to these goals, expectations, policies, and procedures?

  • In the event that deadlines and deliverables are not met, the group will meet with the individual to discuss support for improvement
  • Review how we communicate expectations moving forward to prevent future misinterpretation of team standards