Project: Hang in There!
Group Member Names: Mike Flynn & Brigette Doelp
Goals and Expectations for the Project
What does each group member hope to get out of this project? Mike: A deeper understanding of the fundamental concepts! Brigette: Same! I want to sure up my learning from the lat inning and come to a point where I feel like I can code this in my sleep.
What do we want to achieve as a team? Mike: I want to improve my communication and collaboration skills. Brigette: I want to develop and hone teamwork and team building skills, especially in this remote envrioment.
How will we know that we're successful? If we can wipe the entire project up to the point where we completed, and feel confident that we can redo the entire thing with little issue.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Mike: I'm good at spotting trends in code! I am also strong at keeping a positive enviroment. I need to communicate often to collobrate, and being honest is also good. Brigette: I'm good at pseudocoding and spotting typos! I collaborate best when communication is frequent and honest.
How we can use our strengths to overcome obstacles: We're both strong communicators, so we will communicate well when we do struggle and then we can work towards a solution. Also, we can maintain a positive attitude when approaching a difficult to solve problem.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
Neither of us really have any constraints, however Brigette's time zone difference has been taken into account when setting work times.
Our work schedule will look like this; Project Session Start: 3:30 (Brigette Time) 4:30 (Mike Time) Project Session End: Hard STOP after 3hrs of working. Poms every 25min.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?): Slack when calling isn't viable, Zoom calls during project work time. Decisions will be made 50/50, should a disagreement arise, we will discuss and come to a compromise. We will be open and honest with all well-being communication.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Mike: Functions in general. Brigette: I really want to focus on not overcomplicating everything I approach. I will actively try to find the cleanest solution to the problem we are facing.
Workload Expectations (What features do we each want to work on?): We do not iuntend on dividing up the project by features, instead we are going to alternate driving and navigating. This will ensure that we both have an active hand in ALL code that is written.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): We expect to stick to the Git Flow as is written on the Turing website. We intend on making atomic commits, and using a template for pull requests.
Pomodoro Break Schedule: Every 25-30 min we will take a 5-7 min pom.
Expectations for giving and receiving feedback: Brigette: I expect feedback to be constructive and coming from a good place. I will do my best to do the same. Mike: I expect feedback to be geared to improving any weak areas that were noticed, in a kind manner.
Additional Remote Considerations: Just time zone stuff in general when planning meeting times.
Project management tools we will use (GitHub projects or Trello are popular tools): Zoom, GitHub, Slack, will look into joint calendars.
Day 1 Agenda:
Additional Notes: