---
# System prepended metadata

title: Group Dynamics Worksheet

---

# Group Dynamics Worksheet

## Team Members:

**Leah Ryu**: **Relationship Master**
What technical niche would you like to fill?
* Authentication / databases
* UI 
* Handwriting to font

What personal niche would you like to fill?
* Being a good communicator!
* Art direction!!

**Tate Toussaint** : **Driver**

What technical niche would you like to fill?
* User authentification
* Database management?
* Really anything but UI/Design

What personal niche would you like to fill?
* No buggy code
* Always ahead of schedule
* Willing to accept almost any technical problem

**Tommy Rogers** : <b>Spontaneous Motivator </b> /  Relationship Master

What technical niche would you like to fill?
(2-5 bullets)
* UI/UX
* Widgets
* Gamification

What personal niche would you like to fill?
(1-3 bullets)
* Flexibility
* Ghost 

**Pierce Wilson**: **Relationship Master**
What technical niche would you like to fill?
* User authentication
* Gamification

What personal niche would you like to fill?
* Bonding!

**Amanda Sun** **Spontaneous Motivator**

What technical niche would you like to fill?
* I want to learn React and am down to do web stuff
* I have done backend web asset storage 

What personal niche would you like to fill?
* I want to make sure everyone in the group is heard!
* Snax provider

**Rachael Williams**: **Spontaneous Motivator**

What technical niche would you like to fill?
* not UI
* not particularly interested client/server
* interested in font creation / handwriting conversion

What personal niche would you like to fill?
* advocating for Android app as the only Android user of the group

## 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
* 6:00 PM Mondays
* (Potentially) - 5\:20-6\:30 Wednesday
* (Potentially) Sunday ?

### Responsiveness
*How often should team members be expected to check and respond on Slack?*
* Respond within 24 hours

## II. Decision Making

### Group
*What types of decisions need to be discussed and approved by the entire group?*
1. Which technologies are used
2. Before adding features
3. Before pushing major changes to main
4. Main navigation flow

### One On One
1. Before editing someone else's code

### Individual
*What types of decisions can be made by a single person?*
1. Implementation details 
2. Bug fixes
3. Artistic 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
* **Personal differences**: friction between people due to manner or words said
* **Ghosting**: consistent missed deadlines or lack of contribution

Your group should decide on a plan of action to deal with each type of conflict. There can be multiple levels to each plan. Involving the instructors can be part of the plan.

Try to be as specific as possible.
* A bad plan for Ghosting: “Talk to the person.” (too vague)
* A better plan for Ghosting: “Elect the team member who is closest with that person to check in with them one-on-one. Based on the conversation, reexamine the tasks currently on that person’s plate and revise if necessary. Affirm that they are coming to the next team meeting. At the next team meeting, every team member will make an effort to include the Ghoster in any team discussions.”

### Course of Action
*What will your group do in order to resolve each type of conflict? (include the levels of escalation)*

* **Creative differences**: We have five group members, so we can put conflicts up to a vote after consensus decision making where each person has a chance to talk about the difference, especially the minority voter. If someone really wants to work on something that nobody else agrees is important/wants to work on, they must put in the minimum 10 hrs of work on the main body of work that's been agreed on by the group & spend any extra time they want to on that other feature. We will also rank features by importance as a group at the beginning of the project.
* **Personal differences**: Group members should not be fighting in DMs. We can DM each other to ask about simple tasks such as merging code, but if something becomes an issue, the people who are having a personal difference should start a thread in the main chat (for accountability). 
    Steps:
    1. Both people should agree on an intermediary to resolve conflict.
    2. When possible, assign tasks that minimize overlap of work for a couple of weeks.
    3. Minimize DM conflict.

    At what point should we involve profs? Case-by-case (a difference that cannot be solved over Slack threads with the whole group).

* **Ghosting**: We can start a weekly thread on what we plan on doing the coming week, and make explicit anything that will get in the way of us working 10 hrs/week
    
    Standup each week on either Slack, or during weekly meeting.
    
    Most of us prefer to program on our own, but if someone starts to ghost, we can ask them to attend a mandatory pair programming session with the person they're closest with.
    
    Ghost manager: Tommy (DM Tommy if someone needs to be reached out to). Secondary ghost manager: Tate.
    
    At what point should we involve profs? If they are Ghost Managed 3 times without making it clear in advance that they won't be able to do work... 

The End!

