Skip to content

Instantly share code, notes, and snippets.

@CervAnn
Last active October 22, 2019 20:04
Show Gist options
  • Save CervAnn/38c4ee45e3bec6c11353debd7cc61052 to your computer and use it in GitHub Desktop.
Save CervAnn/38c4ee45e3bec6c11353debd7cc61052 to your computer and use it in GitHub Desktop.
DTR for Lance Cross-Pollination Project

DTR for Lance Cross Poll

Project: Lance

Group Member Names: Sarah Fox, Jake Miller, Jacob Ogren, Ann Cerveny

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

Sarah: Learn front-end and have a deployable product to show for it

Jacob: Learn back-end and have a deployable product to show for it

Jake: Learn GraphQL, get experience mentoring someone in a tech stack that's new to them. / Learn GraphQL and React

Ann: Begin learning and applying facets of React Native, possibly also Vue, and get experience mentoring someone in a tech stack that's new to them.

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

Sarah: Team unifier, the glue Jacob: Help to move the project along, the tugboat Jake: Willing to do whatever it takes to get the project moving, the Leader and the Helper Ann: Thinks of things from all angles; driven by new ideas, and developing creative apps

How we can use our strengths to overcome obstacles: We're willing to do what we need to do to develop something we're proud of.

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

Sarah: 3 phone screenings next week (M, Th) / would like to be done coding by 10:30pm / early riser Jacob: Free in the afternoon/evening / Heavy on the paired programming in the beginning Jake: Phone interview in the afternoon (M) / Will make himself available in the afternoons/evenings Ann: Committed to getting a good nights sleep, but willing to flex where needed / leave by 630pm (Th) / Happy to come in early if it means not staying as late / Likes to take a day over the weekend to work remotely

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 chat / be available Be accountable Show Up

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

Sarah: Learn React and front-end foundations Jacob: Learn how to create and use back-end foundations Jake: Learn GraphQL and the basics of React Ann: Learn back-end foundation (Manipulate databases, Build APIs, Consume APIs)

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

TBD (pending)

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

Use Git Merge Workflow GitHub Project Board - use labels and seperate storyboard by columns For PRs, a BE PR should be reviewed by one of the following: Sarah, Jake, or Jacob; a FE PR should be reviewed by one of the following: Ann, Sarah, or Jacob

Expectations for giving and receiving feedback:

Be kind, make it actionable, be specific

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

GitHub Projects / Google Calendar

Day 1 Agenda:

Initialize your repositories (don’t write any code just yet!) Set up your scrum board with Github projects. You’ll be requireed to use a single board for all repos. This will make it easier to see what everyone is working on during the project. Each student create your goal for something you would like to learn about the other stack (BE student creates learning goal for something about the FE, and vice versa) Normalize on git workflow (we recommend using a “rebase” workflow, as opposed to “merge”, as it is most common on the job) - use a PR template Determine MVP (knowing it could change as the project continues) Create user stories Create wireframes Construct schema design Decide on rough tech stack

Additional Notes:

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