Skip to content

Instantly share code, notes, and snippets.

@julyytran
Forked from rwarbelow/setting_expectations.markdown
Last active February 29, 2016 21:00
Show Gist options
  • Save julyytran/b4bda806252ad63a98c7 to your computer and use it in GitHub Desktop.
Save julyytran/b4bda806252ad63a98c7 to your computer and use it in GitHub Desktop.
Team MountainRacoonJokers
## Setting Group Expectations
Group Member Names:
1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed?
Heidi: Cannot do Tuesday or Weds evening week 5, need to know in advance
Brain: Cannot do Mon evening week 5
July: Cannot do Tuesday week 5 or Saturday daytime week 5
2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
Slack DM's
More is better - avoid doing overlapping work
Ask for help within team first
3. Which feature(s) does each group member *want* to work on? Which feature(s) does each group member *not want* to work on?
Aim for base functionality then do moar funz
Flexible
4. What does each group member hope to get out of the project?
Brian: styling
July: practice, try styling and fun api things
Heidi: flexible
A product we are proud of!!
5. What is the agreed upon Git workflow? What project management tool will be used? What is the agreed upon procedure for conducting code reviews before merging into master: who will review pull requests, and when?
Waffles! Integrate waffle with git.
Heidi will review Brian's pull requests
Brian will review July's
July will review Heidi's
Tag people in pull requests.
Comment in pull request.
If it's important to push in order for someone else to pull, reviews can be overriden.
Rebase BEFORE branch merged to master.
6. What is expected of group members when they run into problems implementing a feature?
Ask for help from the team. Set a time frame on struggle. Be open about it. We all live in struggle city.
7. How does each group member want feedback (both positive and constructive) to be delivered?
Keep it real real.
Start of work time sessions:
1. How you feeling?
2. Where you at?
3. Got any feedback?
8. Is there anything else the group should know about personal work/communication styles?
Force each other to take poms. 50 - 10, sooner if the struggle is too real
Tell Heidi to go to sleep.
Get Brian focused. Be specific about things.
July has two settings: high and low. Let her know if she needs to tone it down or up.
Pair when needed/wanted, divide and conquer to finish, then pair on doing cool things and learn dope things together.
Team lead: July
Topic: gifs for good
-----Project Notes/Ideas------
Possible extensions: stripe, flikr api, ratings - machine learning recs
Incorporate outdoorsy images
Features:
click on gif, description comes up
different gif pricing based on juicyness of gif
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment