Skip to content

Instantly share code, notes, and snippets.

@afg419
Forked from rwarbelow/setting_expectations.markdown
Last active December 8, 2015 01:01
Show Gist options
  • Save afg419/34beef2c45c0eb4d11bc to your computer and use it in GitHub Desktop.
Save afg419/34beef2c45c0eb4d11bc to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Skylark, Starlord, Shrieking Huntress

  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? Available to work before school, except wed fri, otherwise evenings are generally good.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack(for communication), waffle(status)... Clear and explicit conversation everytime we split to individual tasks about expectations etc.

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Penney => {easier: [testing], medium:[css], harder: [logic heavy]} Taylor => {easier: [communicates well, creative], medium:[css, logic], harder: [testing, fixing errors, ruby style, database stuff, pushes through problems as opposed to asking]} Aaron => {easier: [logic heavy, top down picture], harder: [css, managing stress]}

  4. What does each group member hope to get out of the project? Penney => [improve programming skills, better top down view of problems, more confidence in skills] Taylor => [better at pairing and maintaining independence, solid understanding of dbs, http understanding] Aaron => [better at working in the group, everyone should feel valued]

  5. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used? Aaron reviews pull requests -- communicates when they are or aren't merged and why. Aaron's pull requests get okayed by those people working on that content.

  6. What is expected of group members when they run into problems implementing a feature? Communicate that problem and ask for help quickly. -- Taylor Wrestle with it, and then ask for it. -- Penney Communicate it quick. -- Aaron

  7. How does each group member want feedback (both positive and constructive) to be delivered? Penney => Respectfully tell. Wants feedback about her progress. Taylor => Respectfully tell. Wants feedback about his efficiency, communication, and work ethic. Aaron => Respectfully tell. Wants feedback about taking over the project and relinquishing control.

  8. Is there anything else the group should know about personal work/communication styles? Taylor => Wants explanations about edits to code, not to just see them happen.

@rwarbelow
Copy link

looks good!

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