Skip to content

Instantly share code, notes, and snippets.

@hfaerber
Last active October 17, 2019 22:21
Show Gist options
  • Save hfaerber/9511bc738da50b6f412d619a9b510d65 to your computer and use it in GitHub Desktop.
Save hfaerber/9511bc738da50b6f412d619a9b510d65 to your computer and use it in GitHub Desktop.
Commitments:
- Use slack to give a heads up about getting stuck or doing a PR in case the other person doesn't see the email alert.
Then we will move all questions/comversation baout the project to GitHub.
- We must all commit to communicating the things that are NOT going well.
- DTR check-in every 3 days
- Daily check-in 4-4:15pm (pom depending) 5min ish maybe rotating leader?
- We will use a Git Hub Projects as our Project Management Tool
- We can Check in with fist-to-five to dig in to how everyone's feeling.
- Know what we're working
Schedule For Success:
- Lets make sure we are making sure we get the time we need working on non-project practice whether its together or apart.
Austen: working before class is not my best schedule. as late as 6:30pm as an norm, could work later
Weekends - Austen - working before 10 - 10:30am on the weekend doesn't work best
Naomi: may be days she's not up to it and may get quieter or bogged down.
Heather: Isn't usual in great mental shape Friday after class. Prefers to work half day Saturday and full day Sunday.
Communication:
- Communicating in PRs but sending a heads up on Slack
Goals:
What does success look like:
Check-in questions: *Don't want anything to come up in group feedback that we didn't air to each other in the process.
- Are our commits accurately reflecting our contributions?
- Do we feel like we are contributing our fair share? Do we feel our teammates are contributing?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment