Skip to content

Instantly share code, notes, and snippets.

@DougieDev
Last active April 7, 2020 19:34
Show Gist options
  • Save DougieDev/c76e5713cc25ccd0415c2900c40be2f9 to your computer and use it in GitHub Desktop.
Save DougieDev/c76e5713cc25ccd0415c2900c40be2f9 to your computer and use it in GitHub Desktop.
Ideabox: Group Project DTR

Project: Ideabox Group Member Names: Andy, Bill, Dougie

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

Andy & Bill: Increased familiarity with Grid & Flex Dougie: Increased comfort with localStorage and media queries

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

Bill: Research & problem solving

Andy: Objective analytical; Values fairness and equal work from all parties.

How we can use our strengths to overcome obstacles:  Dougie: Utilizing resources in the form of mentors and working developers to assist in roadblocks

Andy: Verbose communication.

Bill: Utilizing research to not allow roadblocks to hinder progress too long.

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

Unanimous: 5pm - 8pm

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

Primary method of communication will be mostly verbal, utilizing Zoom or Slack

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

See first question

Workload Expectations (What features do we each want to work on?): Equal as much as possible

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Utilizing PR templates to shape pull requests, using reference material such as the Turing Git Workflow lesson to help prevent merge conflicts and Git issues

Pomodoro Break Schedule:

No set schedule, take breaks as needed. Roughly 40m of work time with 10-15 min break.

Expectations for giving and receiving feedback:

Dougie & Andy: Immediate and blunt

Bill: Constructive criticism and positive affirmation

Additional Remote Considerations:

Not to let project paranoia interfere with personal non-Turing associated life schedule

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

Trello

Day 1 Agenda:

Format DTR, Day 1 deliverables, incorporate GitHub pages and adding all teammates as collaborators and add project manager. Get started on Iteration 0.

Additional Notes:

 

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