Skip to content

Instantly share code, notes, and snippets.

@bethsecor

bethsecor/setting_expectations.markdown

Forked from rwarbelow/setting_expectations.markdown
Last active December 7, 2015 20:57
Show Gist options
  • Save bethsecor/3e83ee2e2819bc27778d to your computer and use it in GitHub Desktop.
Save bethsecor/3e83ee2e2819bc27778d to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Beth Secor, Toni Rib, Steve Pentler

  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?

  • Toni: Working together M-F before 8pm, work individually after 8pm, Tuesdays with Toni 4- 5:45, Thursdays pairing with Alex 4-5, 10-11 Saturday pairing with mentor

  • Beth: Working together M-F before 8pm, work individually after 8pm, Tuesdays pairing with Jaime 4-5, Mentor meeting wednesday 12-1

  • Steve: Pairing on thursday from 4:15-5:15

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

In person/slack, check-in when working indivudally and stuck on something, reach out to group members when stuck.

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

Want to work on:

  • Toni: Database ActiveRecord

  • Beth: Database ActiveRecord

  • Steve: front-end app, testing with Capybara

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

  • Toni: how models interat with the database. getting comfortable with sinatra routes.

  • Beth: understand the MVC structure really really well.

  • Steve: database and ActiveRecord.

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

When someone makes a pull request, slack the group, whoever is available will review. Each of us will practice making and merging them.

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

Reach out to all group members, do not spend 5 hours trying to fix issue by self.

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

In-person feedback

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

  • Toni: Go to the person you have the problem with first, not to others. Let others know when you want to work on a feature not discussed that day.

  • Beth: Always explain what your solutions to bug fixes are.

  • Steve: Visual learner, draw things out.

Let's take pomodoros!

@rwarbelow
Copy link

Looks good! I might bring the 5 hour limit on question #6 down to <= 1 hour. :)

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