# Group Dynamics Worksheet ## Team Members: **Will Toth** My leadership style (**bold** one): Analyst & Architect / **Driver** / Spontaneous Motivator / Relationship Master What technical niche would you like to fill? (2-5 bullets) While I feel all of us fill the jack of all trades role, I think given that the team prefers backend, my technical niche should be front end. I feel like I have a good knack for data schema choice, but when it comes to implementation, I'd rather work on front end. I am no designer, but I really do enjoy state management, component breakdown, and styling What personal niche would you like to fill? (1-3 bullets) **Chris Long** My leadership style (**bold** one): **Analyst & Architect** / Driver / Spontaneous Motivator / Relationship Master What technical niche would you like to fill? (2-5 bullets) - I have experience with most of the tools that this project might entail - I like maximizing the efficiency of Backend systems - I like to learn new tools that I'm likely to use a lot going forward (one off frameworks aren't exciting or enjoyable for me) I have a personal inclination towards offline tasks when available, e.g. if we decide to use any Machine Learning. However, I have industry experience in Backend, and I have done Full-Stack in previous school projects. What personal niche would you like to fill? (1-3 bullets) - Point person in design decisions and user flow layout - Enhance our application via certain offline tools when possible - Keeping people on time with deadlines **Karsten Kleyensteuber** My leadership style (**bold** one): **Analyst & Architect** / Driver / Spontaneous Motivator / Relationship Master What technical niche would you like to fill? (2-5 bullets) * I enjoy finding solutions to technical problems and finding bugs / analyzing code. * I like to learn new tools and frameworks and would love to do some web dev if we need it * I like implementing ideas and getting into the nitty-gritty of how things work What personal niche would you like to fill? (1-3 bullets) * I want to be a team member who thinks strategically about how to implement technical aspects of the project * I want to increase the productivity of other team members by being available to them if they encounter blockers **Emily Zhou** My leadership style (**bold** one): **Analyst & Architect** / Driver / Spontaneous Motivator / Relationship Master What technical niche would you like to fill? (2-5 bullets) * I enjoy learning about new technical skills and implementing them * I have some full stack experience mainly focusing on back-end functionality but can also take on some database/front-end repsonsiblities if needed * I like problem solving and working with others to come up with efficient solutions What personal niche would you like to fill? (1-3 bullets) * I want to be a team memer who listens to other members to come up with the best solution. * I want to be available to help my team members even if I am not working on said portion. ## 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. Our group's [when2meet](https://www.when2meet.com/?17103006-8d3iA) ### Schedule * Class period Monday, location TBD * Thursday evening * Sunday afternoon ### Responsiveness *How often should team members be expected to check and respond on Slack?* Once a day at least, but utilize tagging someone in the chat to get their attention. Everyone should have notifications on at least to be aware of slack updates. ## II. Decision Making ### Group *What types of decisions need to be discussed and approved by the entire group?* All design decisions though, whether UX related or data schema related, should be communicated to the group before being changed ### Individual *What types of decisions can be made by a single person?* Implementation decisions shouldn't need to be discussed, but rather approved in pull requests. ## 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 can assign a sort ownership over certain aspects of the project. If there is a front end creative difference, then the front end specialist will have more of a say. However, if the rest of the group disagrees, then that will of course overturn the creative difference. In the case of a very split group, we can always consult a professor. * **Personal differences**: Our plan is to address personal differences early such that they do not grow. It is also the responsibility of group members not involved to notice and address personal differences. * **Ghosting**: We are all relatively close and comfortable confronting each other on the matter of ghosting. We are at a point where it would not be weird to confront one another on ghosting The End!