Skip to content

Instantly share code, notes, and snippets.

@grayson-palmer
Last active October 7, 2019 22:16
Show Gist options
  • Save grayson-palmer/097e0f8f6839dca9ea869356504ac6f7 to your computer and use it in GitHub Desktop.
Save grayson-palmer/097e0f8f6839dca9ea869356504ac6f7 to your computer and use it in GitHub Desktop.

Project: Intention Timer

Group Member Names: Nick and Grayson

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

  • Futher solidify code foundation
  • Try something new
  • Practice working with others in-person, not just individual coding
  • Get to know each other better

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

  • Having a roadmap/plan for what the end result is
  • Project planning and expectations
  • Both driver/navigator and independant work

How we can use our strengths to overcome obstacles:

  • Open communication/ask for help/use resources
  • Setting expectations, and if not met identify where/what issues need to be resolved

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

  • Both good with staying after class 1-2 hours, or later if needed.

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

  • Slack is a great tool for us
  • Meet up in morning or at lunch for quick check-in in person

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

  • Strenghts:

    • Open communicators
    • Code organization
  • Growth:

    • Better at co-working and collaboration
    • Git collaboration

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

  • Realistic expectations and milestones

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

  • Unknown

Expectations for giving and receiving feedback:

  • Both agree with giving candid/blunt criticism...just don't be a dick

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

  • Trello

Day 1 Agenda:

  • Disect project requirements
  • Wireframe
  • Begin HTML

Additional Notes:

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