---
# System prepended metadata

title: Group Dynamics Worksheet

---

# Group Dynamics Worksheet

## Team Members:

**Georgia Mandell**
My leadership style:
**Analyst & Architect**  /  Driver  /  Spontaneous Motivator  /  Relationship Master

What technical niche would you like to fill?
* I don't love working with websites so I would like to take any offline tasks 
* I love design and aesthetics so I would like to be involved in the UI
* I am very detail oriented and think I could be helpful in the debugging process 

What personal niche would you like to fill?
* I want to be someone who encourages the team to switch it up when we are in a rut-- whether that means working outside, in a different location, or chatting over dinner instead of on his laptop


**Phoebe Ford**
My leadership style:
Analyst & Architect  /  Driver  /  **Spontaneous Motivator**  /  Relationship Master

What technical niche would you like to fill?
(2-5 bullets)
- I enjoy logic and solving puzzles, so I can be a problem solver in the group how helps to think out different approaches to problems if someone or the group is struggling with an issue.
- I have limited exposure to front-end development, but I have gained lots of experience with testing back-end code and debugging approaches, so I am happy to heavy hand in the testing phase.

What personal niche would you like to fill?
(1-3 bullets)
- I want to serve as someone who inspires creativity and thinkig outside of the box,  and as someone who grew up with a learning disability I also think I can offer insight into what might be helpful in education products directed at youth. 

**Giorgie McCombe**
My leadership style:
Analyst & Architect  /  Driver  / Spontaneous Motivator /  **Relationship Master**

What technical niche would you like to fill?
* I'm interested in working on designing and revising the UI to make sure it's as intuitive as possible through usability testing. I don't have a ton of experience with frontend, but am eager to learn more about it.
* In general, I'd be happy to work on learning any new technology
* I'm also taking a database class right now, so if our implementation needed to use one I would want to work on that.

What personal niche would you like to fill?
* I want to be involved in bringing in new ideas/asking questions
* I want to bring energy and fun to team meetings 

**Jacob**
My leadership style: **Analyst/Architect**

What technical niche would you like to fill?
(2-5 bullets)
* Interested in algorithm design/ML if that becomes relevant
* Can do web dev, but please no UI/UX
* Generally happy to help debug 
* Definitely interested in user research

What personal niche would you like to fill?
(1-3 bullets)
* I want to help set priorities & make sure we're intentional in product decisions
* Generally, want to make sure vibes are good


**Gwen**
My leadership style:
**Analyst & Architect**  /  Driver  /  Spontaneous Motivator  /  Relationship Master

What technical niche would you like to fill?
(2-5 bullets)
* I enjoy coming up with different approaches to solving problems and debating what the best way is
* Problem solving 
* I am happy to do whatever is needed, the only exception is that I am not the best designer but I can always give it a try if we need 

What personal niche would you like to fill?
(1-3 bullets)
* I am good at conflict resolution and helping people see both sides of situations 
* Making sure we keep things fun when the work gets hard/stressful 


Nick Irwin
My leadership style:
Analyst & Architect / **Driver** / Spontaneous Motivator / Relationship Master

What technical niche would you like to fill?
- I love learning about new packages / libraries so I would like to be the one to try out something new or explore new technologies
- I also have had some practice building websites and so I would be able to take responsibility for anything online

What personal niche would you like to fill? 
- I will probably be the one to remind the group of the long-term implications of certain decisions since I like to think far in advance 

## I. Communication
*You are required to spend at least 10 hours/week outside of class. Outline a general weekly meeting schedule with at least 1 time that everybody can make. That one meeting must include the entire team in the same room, in person. The rest of the 10 hours may be split into several sessions throughout the week. A nice tool for this is [when2meet](https://www.when2meet.com/).*

### Schedule
* 3:30-5:20 on Mondays and Wednesday (either in class or over Zoom)
* Tuesdays / Thursdays at Noon
* Friday at Noon

### Responsiveness
Team members should be responsive when we are trying to plan meetings / coordinate sessions. In general, a member should be checking the group chat at least once a day. 

## II. Decision Making

### Group
*What types of decisions need to be discussed and approved by the entire group?*
* Decisions that affect the general direction of the project / problem statement
* Adding or removing features
* Changing existing code 
* Setting meeting times - subgroups shouldn't meet without notifying others 


### Individual
*What types of decisions can be made by a single person?*
* Making decisions about task you were assigned, we always go back and re-evaluate decisions someone was unsure about
    * ie. it may be up to the individual how to implement a certain feature, but it's not up to the individual to decide what features to work on/create
* Person can also ask for help on decisions


## III. Conflict Resolution
There are three main types of conflict that tend to occur in group projects:

* **Creative differences**: disagreement on any decisions related to the product
    * Plan: make a pros and cons list for the decisions, if the group can't come to a consensus we will have to take a vote and have to get majority to make any change. Also we can ask Tim.
* **Personal differences**: friction between people due to manner or words said
    * Plan: normalize airing your grievances with each other so that we don't let tension build up 
    * We all agree that it is okay to be annoyed at people and talk about it 
    
* **Ghosting**: consistent missed deadlines or lack of contribution
    * Discuss with them what they want to work on or may be more interested in so that they contribute in ways they care.
    * Figure out what might be a busy week for everyone and then allocate work based on that (give and take, its a marathon not a sprint etc)
        * Speak up when you have a lot going on/check in with eachother about workload



The End!
