P2 Checkpoint 0: Team Norms

P2 TEAM RHIZ AGREEMENT

1. INTENT & VISION:

All members of “Team Rhiz” agree to follow the terms of this agreement. Our vision is to deliver quality work on time, with all requirements met before submission (“A-level” assignments). While our project may not be start-up-ready by the end of the quarter, we care about high-quality design and creating a useful, non-trivial product. We also intend for our team dynamic to be enjoyable and friendly by incorporating play into our interactions.

2. ROLES:

Each week, we will delegate roles for each assignment based on our self-declared strengths. For some assignments, it will look like each person is taking on portions of the assignments that cater to their strengths. For other assignments, this will look like each person taking on the same tasks. Regardless, each team member must take accountability and ownership of the final submission by reviewing it as a whole.

  Strengths Would rather not do
Divyesh
  • Recruiting/talking to people
  • Designing on Figma
  • Ideation/thinking
  • Making simple slides
  • Writing
  • Planning
Zerui
  • Writing
  • Programming
  • Designing
  • Talking to people
  • Make slides
Yixun
  • Writing drafts
  • Visual Arts
  • Little Programming
  • Make slides
  • Programming /technical
Joseph
  • Artistic Design
  • Mechanical ideation
  • Talking to people
  • Story ideation
  • Technical stuff
  • printing/writing
  • Refining established products
Clare
  • Turning everything in
  • Going from design to app
  • Making slides
  • Writing long drafts
  • Starting a design

 

3. PROMISES:

We each promise to complete the work we commit to at a high quality, so that others do not need to redo it (e.g., do not rely on low-quality AI-generated work). We will communicate as early as possible if we anticipate difficulties meeting deadlines or encounter any roadblocks. We also promise to take initiative in taking on work rather than waiting for tasks to be delegated. Task assignments will be finalized during our weekly meetings.

4. TIME / VALUE:

We agree to meet weekly on [insert day] at [insert location] at [insert time] to finalize the assignment due on [Thursday?] and delegate responsibilities for the next assignment. We will coordinate asynchronously over text for ongoing work.

5. MEASUREMENTS OF SATISFACTION:

Our measure of success will be strong assignment grades (A-/A level) and an equitable distribution of contributions across the team. Our measure of successful team dynamics will be low frequency of conflicts and minimal time spent on interpersonal disagreements.

6. CONCERNS AND FEARS:

We are concerned that unresolved tensions may build up and negatively impact the group. Additionally, group members have experienced lapses in communication (including around travel or availability) leading to team misalignment in the past, requiring members to take on a disproportionate amount of assignment work. We fear we may run out of time and need to reduce project scope.

7. RENEGOTIATION:

We recognize the importance of ongoing communication. Team members should proactively initiate conversations as early as possible to renegotiate responsibilities when circumstances change (e.g., during busy weeks or due to personal commitments).

8. CONSEQUENCES:

We believe that the team as a whole makes better decisions than any individual. We agree to collectively determine appropriate consequences for any violations of this agreement. If there is a violation to the team agreement, it should be addressed through an open and honest discussion. Our goal is to learn from these situations, prevent future issues, and maintain transparency around concerns and feelings, rather than impose punitive measures.

9. CONFLICT RESOLUTION: We agree to the following rules:

1) Talk DIRECTLY to the person or group you are in conflict with

2) If needed, get the entire team involved

3) Have open space to think about next steps and what changes can be made

10. AGREEMENT: We agree to value each other’s ideas and dedicate time to create a pleasant and fruitful learning environment in this class.

 

About the author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.