Skip to content

Instantly share code, notes, and snippets.

@samlandfried

samlandfried/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Last active April 10, 2017 20:32
Show Gist options
  • Save samlandfried/4c131ff59eabf2b7575fdde4dc68eadb to your computer and use it in GitHub Desktop.
Save samlandfried/4c131ff59eabf2b7575fdde4dc68eadb to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Danny Radden, Jonathan Kidd, Maria Stenquist, Sam Landfried

  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?

Check Google Calendar project

Group: After class - 7 pm Maria: Birthday on Saturday. Wants to meet mornings. Jonathan: Can't do Thursday night, or Sunday. Danny: Wednesday probably can't meet, next Tuesday has a pairing. Sam: Monday, Tuesday, Thursday after 7 are no gos. Danny and Sam take Thurs 4-6 for Woz.

  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • We can communicate on our Slack channel.
  • Daily standups and retro.
  • Standup at 1 pm (Or when worktime starts).
  • Retro at 630 pm.

Stand Up ?s

  1. What are your objectives for the day?
  2. Are there any technical sticking points?
  3. What support would be helpful?
  4. Any proposed changes to workflow?
  5. What merging strategies should be considered?
  6. What should we call this instead of merging?

Retro ?s

  1. Highlight. What could have been better

  2. Are you on track?

  3. What's puzzling you at this moment?

  4. Do you feel like you're being heard/listened to?

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

Do Factory Girl as a group. Auth/Auth stuff as a group. J: wants exposure to each part. Danny: wants to write 0 tests. Maria: wants to write tests. Sam: styling

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

Danny: Wants to Maria: Learn as much as possible. Jonathan: Synthesis. Pulling together what we've studied for the past few weeks. Sam: Synthesis.

  1. 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?

Git workflow: Work on separate branches Push branch to Maria PR to master The pair that does not make the PR must do code review and merge (ASAP) Maria handles merge conflicts Push to Heroku (If it's not ready for Heroku, it's not ready for master)

Project management tool: Waffle Google Drive for holding retro notes

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

If struggling for 30 minutes with no progress, seek outside help.

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

Jonathan: Face to face. Wants to know if there's a problem. Maria: Wants ASK feedback. Project non-relevant stuff can be put on hold. Sam: Wants it early in the day. Danny:

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

Maria: Introvert Jonathan: Introvert Show sensitivity to need for breaks and sensory overload. Important to assert your opinions.

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