Skip to content

Instantly share code, notes, and snippets.

@kawilliams8
Last active March 20, 2019 02:46
Show Gist options
  • Select an option

  • Save kawilliams8/3e7c6f39f3dbed3723de4210a17f4e0b to your computer and use it in GitHub Desktop.

Select an option

Save kawilliams8/3e7c6f39f3dbed3723de4210a17f4e0b to your computer and use it in GitHub Desktop.

Project: Number Guesser

Group Member Names: Hindreen and Katie

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 want to finish the project with all of the "proficient" standards and as many "exceptional" standards as time allows, improve our understanding of the concepts involved, and both be able to explain all components of the project. Success also includes strong communication.

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

From a quick discussion, it seems we have many of the same fears and concerns, but approach them from similar perspectives. We both value research and experimentation.

How we can use our strengths to overcome obstacles:

When a component is ready to be tested, we can trust each other's analytical mind to give strong feedback.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

Hindreen: Doesn't prefer early mornings or late nights, but is currently doing both. Will text at any time with the expectation that Katie's phone is silent. Replys aren't expected immediately. Slack messaging for all communication, even on the weekends. Computers must be monitored on weekends.

Katie: More of a night owl. Will make sure her phone is silent so she doesn't feel compelled to stay up late and respond. Is allowed to message Hindreen always, and he will also have his phone silent when necessary. Slack messaging for all communication. Computers must be monitored on weekends.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): See above. Communication (messages, in person) every single day. All team decisions will be based on conversations, focused on our progress, not emotion. Decisions will be implemented, with follow up communication on the implementation.

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

Hindreen: Sees a great opportunity in this projects. Others' perspectives are valuable to learn the most.

Katie: Excited to learn and experiment with JavaScript and GitHub.

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

We both want to have some time in the parts we are already comfortable with, then purposely switch to work on the other components. The goal is to understand every component in detail.

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

Hindreen will start researching the JavaScript components; Katie will start with GitHub set up.

Expectations for giving and receiving feedback:

Respond to all communications, even if just an emoji to show that it was read.

Project management tools we will use:

GitHub, CodePen/Repl, in person communications, To Do lists (possibly within GitHub or Slack)

Day 1 Agenda:

Start researching GitHub workflow and some JavaScript features. Play with a sample repo to learn two person GitHub.

Additional Notes:

Let's have fun and learn new things!

@allisonreusinger
Copy link

I really appreciate how you've laid this out and set boundaries for self-care! Nice work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment