Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save Claudia108/22de995a4bcf33e283eb362c71d0a615 to your computer and use it in GitHub Desktop.
Save Claudia108/22de995a4bcf33e283eb362c71d0a615 to your computer and use it in GitHub Desktop.
Setting Expectations

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?
  • Mon: except Claudia(4.15-5.15pm)
  • Tue: except Claudia(6.15-7.15pm)
  • Wed: except Ling(7-9pm), Patrick until(6pm)
  • Thu: open - until 9pm
  • Fri: except Claudia(until 7pm)?
  • Sat: start at 11am
  • Sun: start at 11am
  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • daily, more often
  • Slack, in person
  • screen hero
  • share phone numbers
  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? All members are interested in:
  • design, styling, using materialize

  • integrating maps (map box, google) - as extension

  • touching most of the code

  • Split up work into pairs

  • Decide everything structural together (routes, testing structure, models, basic design)

  • Write user stories together - split those user stories

  1. What does each group member hope to get out of the project?
  • Patrick: styling with materialize, learning to include maps
  • Ling: best possible work in group,
  • Matt: working knowledge how to set up a reails project with deep back end and beautiful front end
  • Claudia: styling and learning to include maps, getting more comfortable with general setup with routing, session,...
  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?
  • alerts via Github
  • assign tasks on waffle - everyone gets waffle card
  • assign project owner per feature
  • check on open pull requests in the morning - other member merges request.
  1. What is expected of group members when they run into problems implementing a feature?
  • ask for help after working for an hour
  • ask via slack or in person or screen hero
  1. How does each group member want feedback (both positive and constructive) to be delivered?
  • debrief daily before leaving the group
  • written feedback in the first days (Wed or Thu)
  • open and direct communication in person
  1. Is there anything else the group should know about personal work/communication styles?
  • give feedback about strong communication style
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment