Skip to content

Instantly share code, notes, and snippets.

@matt-stj
Forked from rwarbelow/setting_expectations.markdown
Last active November 9, 2015 17:52
Show Gist options
  • Save matt-stj/e2396990cbbd09e5630d to your computer and use it in GitHub Desktop.
Save matt-stj/e2396990cbbd09e5630d to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Edgar, Matt R., Matt S.

  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? We'll shoot to work after school most days, trying to accomodate little schedule differences as they come. Flexible on weekends.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Started a slack chaneel #Mattgar + texting. Anytime we separate to work on home, we'll plan on checking it at the end of each day to realign/help each other with problems they're having. We'll likely be pairing together most of the time, with the exception of smaller/repetitive tasks. Shoot to set mini-milestones/goals and chip away at those instead of falling behind or getting overwhelmed with the scope of the entire project.

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Edgar + Matt R want to get their hands on some Materiaize. We'll try to split tasks up evently so everyone gets a chance to touch different parts of the code.

  4. What does each group member hope to get out of the project? Edgar wants to come out with a stronger foundation in authorization/authentication.

  5. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used? Never work on master. Use waffle - check out cards when working on features and issues. First person to see PR, who didin't submit it, will review/merge.

  6. What is expected of group members when they run into problems implementing a feature? Try to figure it out. Don't spend longer than 30 minutes trying to figure it out. Get help early and often.

  7. How does each group member want feedback (both positive and constructive) to be delivered? Be honest with one another about our comfort level with features that we're taking on -- open lines of communication for everything.

  8. Is there anything else the group should know about personal work/communication styles? We all prefer to tackle problems together and only split up if we're confident in our abilities to not waste time.

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