Skip to content

Instantly share code, notes, and snippets.

@TheKaterTot

TheKaterTot/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Last active February 21, 2017 21:19
Show Gist options
  • Save TheKaterTot/d74efc68c0ba30437d70945ff2affea9 to your computer and use it in GitHub Desktop.
Save TheKaterTot/d74efc68c0ba30437d70945ff2affea9 to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Ashley, Edilene, Amara, Katy

  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? Ashley: Evenings until 6 or 7. Independently until about 10. One day free on weekends to recuperate. Edilene: Available until 7 or 8. Not a lot of commitments. Saturday not good. Amara: Daughter some days. Sleeps at 7. Work independently until about 10. Tuesdays not good for group. Birthday party on the weekend. Katy: Available until 8 or 9.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack to communicate. Check it often.

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Ashley: Styling Amara: UX, user stories, Katy: Authorization Edilene: None

  4. What does each group member hope to get out of the project? Ashley: Completed with 3s. Would like to do an extension. Good workflow. Edilene: Cement knowledge of Rails apps and relationships. Amara: Better understanding of many to many. Complete functionality. Nice-looking app. Katy: Complete functionality and styling.

  5. 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? Slack out notices for PRs. Dev branch and master for production. Two approvals before merge.

  6. What is expected of group members when they run into problems implementing a feature? Send out a Slack message letting the group know and asking for input. Don't spend too long on an error (more than 30min).

  7. How does each group member want feedback (both positive and constructive) to be delivered? Amara: Direct and in the moment. Edilene: Verbally, don't wait too long. Ashley: Will accept feedback as long as it's respectful. Suggestions for solutions are helpful. Katy: Say something specific about a changeable behavior.

  8. Is there anything else the group should know about personal work/communication styles? Ashley: Can get stuck on problems, likes to work independently. Would like to know if she's digging in too much to an issue. Edilene: Amara: Katy: Can be stubborn defending strategies.

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