Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save eoneill23/eb9db92a36f6aad4330320a93fd57a1d to your computer and use it in GitHub Desktop.
Save eoneill23/eb9db92a36f6aad4330320a93fd57a1d to your computer and use it in GitHub Desktop.
Eric O'Neill and Julian Enochs-Brown DTR Memo Number Guesser

Project: Number Guesser

Group Member Names: Eric O'Neill & Julian Enochs-Brown

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

  • To get better at JavaScript
  • Finish phase 1 and start phase 2 by Thursday, May 9.
  • Work on the project every day.
  • Get comfortable pairing.

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

  • Julian is more creative and Eric is more analytical.
  • We are both confident.
  • We are strong-willed and determined to create an exceptional project.

How we can use our strengths to overcome obstacles:

  • We are both hard-working, so we will be able to push through obstacles and have a growth mindset.

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

  • We are available to stay until 6:30 on the weekdays after school to work.
  • On the weekends, we are both pretty open to work after 11 am and until we get done what we need to get done.

Communication Expectations (How and how often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

  • Talk every day.
  • Our primary communication method will be Slack.

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

  • We both feel fairly confident in our HTML and CSS.
  • Neither of us have any prior JavaScript exposure, so we are both wanting to improve our JavaScript knowledge through this project.

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

  • We're not sure how creating each feature will be delegated, but we will split the workload as evenly as possible.

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

  • We're planning using GitHub, but we're not exactly sure what the workflow will look like at this moment.

Expectations for giving and receiving feedback:

  • Just be candid.

Project management tools we will use:

  • Google calendar and Slack

Day 1 Agenda:

  • Wireframe
  • HTML
  • As much CSS as possible

Additional Notes:

@allisonreusinger
Copy link

Great level of detail here, nice work on setting expectations!

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