Intention-Timer-DTR.txt

Project: Intention Timer

Group Member Names: Hanna Kim, Chadrick Dickerson, Nick Hart

Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):

We definitely want to meet all of the technical learning goals - to develop a better understanding of clean semantic HTML, CSS and dry JavaScript that adheres to SRP, event bubbling and delegation, local storage. We want to prioritize learning over completion.  

With this also being our first group project, we want to learn to navigate group dynamics as developers. This also includes efficient git workflow.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

We're all inherently collaborative people, and are very team oriented. We enjoy working in group settings because it's a valuable way to learn, and we enjoy helping each other learn.

How we can use our strengths to overcome obstacles:

We're not afraid to turn to each other to ask for help. Three minds are better than one. Three's a party. Three's a company. We're like the three muskateers.

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):

We're planning on taking full advantage of the project work time we'll have in class. Aside from that, our plan is to meet after 6 and until 10 when needed on weekdays, and we'll play it by ear for the weekend.

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?):

We'll plan on staying in touch daily via slack. We have our phone numbers posted in the channel if slack goes down.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

The areas we feel least comfortable in include CSS, event bubbling, function control flow, passing arguments into functions and seeing opportunities to refactor code.

Workload Expectations (What features do we each want to work on?):

We'll plan on starting with driver navigator, and divying up the work as best we see fit as we go.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

We're planning on building on all the habits that we've put in place so far, from pseudocoding to using a PR template and code reviews.

Pomodoro Break Schedule:

We'll follow a regular pom schedule, close to 30 minutes on, 10 minutes off, with a longer break every 4 poms.

Expectations for giving and receiving feedback:

We'll follow Turing's template for feedback, keeping things actionable, specific and kind. We're all open for direct feedback.

Additional Remote Considerations:

No real logistical considerations other than the scheduling ones, which have been discussed earlier. Communication wise is the same as above.

Project management tools we will use (GitHub projects or Trello are popular tools):

We'll use Github projects.

Day 1 Agenda: The plan will be to tackle iteration 0 and see how far we can go - we'll base the rest of the schedule on how tomorrow goes.