Skip to content

Instantly share code, notes, and snippets.

@ToniRib
Forked from rwarbelow/setting_expectations.markdown
Last active January 11, 2016 17:31
Show Gist options
  • Save ToniRib/0d5c1038439341e23936 to your computer and use it in GitHub Desktop.
Save ToniRib/0d5c1038439341e23936 to your computer and use it in GitHub Desktop.
Setting Expectations - Little Shop of Orders

Setting Group Expectations

Group Member Names: Toni Rib, Brenna Martenson, Taylor Moore

  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?
  • Toni: Tuesdays w/Toni 4:15-5:45pm, Thursday w/Alex 4-5pm, next Wed w/Alex 4-5pm, next Thurs w/mentor 5pm-7pm, Horace bitcoin 4pm-5pm
  • Taylor: mentor meeting at some point, probably Wed or Thurs
  • Brenna: friend in town on Thursday, dinner at some point with them
  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • Slack, in person
  • chat in Slack if you are going to take on extra responsibility separately
  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
  • Taylor:
    • want: css (as long as it isn't standard materialize), ActiveRecord
    • not want: nope
  • Brenna:
    • want: ActiveRecord, setting up a flow
    • not want: nope
  • Toni:
    • want: mode relationships, authorization
    • not want: nope
  1. What does each group member hope to get out of the project?
  • Brenna: awesome at rails!
  • Taylor: better understanding of activerecord, good workflow
  • Toni: where to start, dealing with how a project evolves
  1. 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?
  • use factorygirl & minitest
  • waffle
  • at least one other person than the person who made the pull request has to do a code review
  • commit messages: command form (imperative present tense), first word capitalized, subject no longer than 50 chars, body when possible
  1. What is expected of group members when they run into problems implementing a feature?
  • ask questions (in slack, in person) after 20 minutes if no progress has been made
  1. How does each group member want feedback (both positive and constructive) to be delivered?
  • in person!
  • just confront someone about it and give reasons (why you might be editing someone's code)
  1. Is there anything else the group should know about personal work/communication styles?
  • tell Taylor if he isn't "all there all the time" to make sure he contributes
  • tell Toni if her ideas are being heard too loudly
  • ^ same with Brenna
  • Toni may have to step away for 30 minutes to collect herself if she gets too stressed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment