Skip to content

Instantly share code, notes, and snippets.

@jasonpilz

jasonpilz/setting_expectations.markdown

Forked from rwarbelow/setting_expectations.markdown
Last active November 9, 2015 17:44
Show Gist options
  • Save jasonpilz/21d0153c5c680fbb0d37 to your computer and use it in GitHub Desktop.
Save jasonpilz/21d0153c5c680fbb0d37 to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Emily, Sekhar, Jason

  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?
  • Emily - not 4-6pm, avail 6-9pm, pref sat over sunday
  • Sekhar - anytime, FLEXIBLE!
  • Jason - weekdays flex to stay, pref sat over sunday
  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • Slack primarily, exchange tel number as backup, always be available on slack, have phone on you.
  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
  • Sekhar - front end, flexible
  • Emily - flexible
  • Jason - flexible, but would like to focus on front end related tasks.
  1. What does each group member hope to get out of the project?
  • Emily - Learning to implement the whole process with minimil referencing
  • Sekhar - to have a portfolio-quality project from start to finish
  • Jason - to focus on the workflows, git and driving developement from the tests.
  1. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used?
  • Any in progress work is done on a branch
  • Minimum one other person to review pull request, if needed both other members can be requested to take a look.
  • When pull request is submitted, slack message will go out requesting review for one of other 2 members.
  • Waffle for project management
  1. What is expected of group members when they run into problems implementing a feature?
  • Alert others on slack when you run into a problem / can't finish what you planned to complete.
  1. How does each group member want feedback (both positive and constructive) to be delivered?
  • Emily - verbal, be open before gets worse
  • Sekhar - catch things before they get out of control, don't bottle it up. Don't sugarcoat
  • Jason - verbal preferred.
  1. Is there anything else the group should know about personal work/communication styles?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment