Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save caward12/a9da978b81d499836747f549749a31f6 to your computer and use it in GitHub Desktop.
Save caward12/a9da978b81d499836747f549749a31f6 to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Beth Knight, Sergey Lukyanenko, Craig Ness, Colleen Ward

  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?
  • Beth needs to pick up her dogs at 7
  • free weekends
  • in general, we have no lives outside of Turing.
  • Sergey, Colleen and Craig can stay until 7/8
  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • slack - direct group
  • daily retro to come back together
  • waffle
  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
  • Beth - feature testing
  • Sergey - styling
  • in general we want to work on all parts of the project.
  1. What does each group member hope to get out of the project?
  • Strive for fours!
  • Portfolio worthy site that we would all be proud to show potential employers
  • Good group harmony
  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?
  • Merge when we are all together so we can do final review as a group. Individual review on our own. Project management tool - Waffle
  1. What is expected of group members when they run into problems implementing a feature?
  • Struggle for a bit and then reach out to group memebers for help. And then as a group we can reach out further.
  1. How does each group member want feedback (both positive and constructive) to be delivered?
  • In person Bring it up sooner rather than later so it doesn't become a bigger deal.
  1. Is there anything else the group should know about personal work/communication styles?
  • Beth goes to bed early. (9pm)
  1. How can we leverage each other's strengths?
  • Colleen - rails and ruby logic

  • Sergey - testing and keeping up with current flow - reminding us about going back to 'fix' something. Has an eye for details.

  • Craig - Good project manager! Cautious - in a good way - methodical. Even temperment.

  • Beth - Faker, factory girl, css/bootstrap, open to trying new approaches, idea-generator, loves to drive

  • Maintain current github workflow; make sure we continue to do stand ups/retros; test different pairings within the group - improve efficiency

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