# Group Dynamics Worksheet

## Team Members:

**Megan Ren**
My leadership style (**bold** one):
Analyst & Architect / **Driver** / Spontaneous Motivator / Relationship Master

What technical niche would you like to fill?
(2-5 bullets)
* I love doing deep research dives into product concepts -- exploring existing competitors, gathering background information on the field, analyzing and synthesizing that info
* I might not be a software whiz but I'm persistent when it comes to problem-solving. I'll chase a bug down fifty different files and between twenty functions (even though it'll probably take me all day). Willing to open as many Stackoverflow tabs as it takes to get a working solution in code
* I have rudimentary but sufficient skills in UI/UX design (Figma, Adobe Illustrator/Photoshop, knowledge of wireframing/hi-fi/etc)

What personal niche would you like to fill?
(1-3 bullets)
* I want to be a source of motivation on the team, making sure that everyone is working on something that's exciting to them and that they actively want to work

**Ben Korkowski**
My leadership style: **Analyst & Architect**

What technical niche would you like to fill?
(2-5 bullets)
* Gain exposure in front-end web development and be able to actively converse in the entire process from design to implementation to use
* Be able to create clean and efficient code that is easily understandable by all team members
* Become well versed in Github and correctly integrating various components into the bigger project

What personal niche would you like to fill?
(1-3 bullets)
* Be seen as someone who people see as being diligent and knowledgable about their work and able to explain my process and ideas for others benefit
* Have a positive impact in pushing through group difficulties and also knowing when to pivot or trim expectations when necessary

**Isaac Feldman**
My leadership style (**bold** one):
**Analyst & Architect**

What technical niche would you like to fill? (2-5 bullets)
- I love a complex problem! If there's something technical and scary: I'm game.
- I'm a messy thinker, but a clean coder. I'd like to get super involved in design and also help out with maintaining our tooling and documentation

What personal niche would you like to fill? (1-3 bullets)
- I'd like to challenge myself and others to think deeply about a problem; I won't settle for "it is this way because it always has been"
- I want bring our team together, just because we're solving hard problems doesn't mean we can't have fun!

**Ben Fernando**
My leadership style (**bold** one): **Analyst & Architect** / Driver / Spontaneous Motivator / Relationship Master

What technical niche would you like to fill?
(2-5 bullets)
- I am more experienced with backend work but would definitely be willing to branch out
- I enjoy learning new tools/languages so would be very willing to experiment with things we are unfamiliar with
- I actually like going through code and bug checking so would help check over work that isn’t working or double checking

What personal niche would you like to fill?
(1-3 bullets)
- I enjoy working in groups and collaborating in meetings or coding sessions
- I will not take anything personally so please come with issues or concerns so we can work them out
- I want to be a helpful sounding board to flesh out ideas and work through difficulties

**Mark Tao**
My leadership style (**bold** one):
Analyst & Architect / Driver / Spontaneous Motivator / **Relationship Master**

What technical niche would you like to fill?
(2-5 bullets)
* I'm decent at doing like a lot of the kind of "pre-setup" stuff? Like for for this project, I sort of understand that we're going to have to read up extensively on how Google Chrome/Safari works, and tie in what we already know with what we want to do.
* For the most part, I sort of enjoy coding/designing together. I often find that when I'm forced to kind of explain things to people, I'm able to better understand what I'm doing.
* I think I can also do a lot of like the nitty gritty implementation. The stuff that's pretty deep in the weeds and whatnot.
* I also enjoy exploring and researching sort of "new" things? I'm sure there are plenty of people already iterating/working on this kind of process, and I'd be happy to sort of look at what they're doing.

What personal niche would you like to fill?
(1-3 bullets)
* I think I'm kind of a fan of like us hanging out outside of this? Like I genuinely enjoy sort of getting to know people, and I honestly think it really does help with like coordination and teamwork.
* I guess I also decently okay at conflict resolution? Like I usually consider myself decently fair at like ensuring that there isn't anything major affecting us.

**Jason Chen**
My leadership style (**bold** one): **Analyst & Architect** / Driver / Spontaneous Motivator / Relationship Master

What technical niche would you like to fill? (2-5 bullets)
- I dislike solving bugs and working on the nitty gritties, and instead prefer to work on the bigger picture idea, such as the design of the software.
- I’d like to try to make sure that our product is easy to use and intuitive.

What personal niche would you like to fill? (1-3 bullets)
- I want to make sure that everyone feels supported and empowered.
- I want to be someone who is collaborate and easy to work with.

## 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
* Saturday - 3:00 pm (Library/CECS)
* Wednesday - 3:30 to 4:30 pm (Library/CECS/Zoom)
* Sunday - 3:00pm (Library/CECS)
* Thursday - 4:15 to 6:15 pm (Library/CECS)

### Responsiveness
* Everyone checks slack 2 to 3 times per day and should have notifications on. In an emergency or non-responsiveness, you can @someone directly.

## II. Decision Making

### Group
* Any "big" decision like big, over-arching design decision, and deciding when to move on.

### Individual
* Individual implementation stuff, self-driven research, and specific tasks.

## 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**: Meet in person, and discuss the pros and cons of each of the choices. Ideally should be unanimous, and if necessary, consult someone else.
* **Personal differences**: first-level escalation, reach out directly. second-level, reach out to the relationship master. third-level, reach out to the group. fourth-level escalation, if necessary, just bring in the prof.
* **Ghosting**: first-level is directly reaching out through other avenues. second-level, talk with them in or after class in person. third-level, outside help.

The End!