Skip to content

Instantly share code, notes, and snippets.

@acareaga

acareaga/setting_expectations.markdown

Forked from toriejw/setting_expectations.markdown
Created November 9, 2015 17:46
Show Gist options
  • Save acareaga/6c2763a6ed0be8f110a5 to your computer and use it in GitHub Desktop.
Save acareaga/6c2763a6ed0be8f110a5 to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Aaron Careaga, Cole Hall, Torie Joy-Warren

  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?

Torie can't work Saturday. Aaron wants to ski on the weekend in the morning, and meets with a mentor on Tuesday evening (5:30). Cole has mentoring for ~ an hour Tuesday and Wednesday after wrap-up. Cole likes to have some evening time, which we all like. Friday night is not good for us, after ~6.

  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

Slack, Github, person, comments, waffle.io, smoke signals. Daily communication.

  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?

Cole: wants to work on it all. Aaron: same boat as Cole. Torie: wants to do everything except styling.

  1. What does each group member hope to get out of the project?

Stronger understanding of rails, solidify module 2, goal: done a day (Tuesday night!) before to allow time for refactor and not be stressed, have something to show future employers

  1. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used?

Waffle.io will be used for project management. PR reviews will be done by whoever is most tied to the thing being pushed who is not the pull requester. No one will merge their own PR to master. Torie will push to heroku when PR is merged to master. Checkout branches with name of waffle card names! And make sure to close it out on waffle.

  1. What is expected of group members when they run into problems implementing a feature?

Keep a cool head, ask for help. Keep open communication and let others know what you're stuck on. BE DIRECT :)

  1. How does each group member want feedback (both positive and constructive) to be delivered?

Don't hurt feelings. Don't be mean with your feedback. Be straight up. In person is best.

  1. Is there anything else the group should know about personal work/communication styles?

Concern about skill level (fear of slowing down vs. understanding). Focus on communication/team skills.

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