Skip to content

Instantly share code, notes, and snippets.

@CjMoore

CjMoore/setting_expectations.markdown

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

Setting Group Expectations

Group Member Names: Charlotte, Courtney, Valerie, Casey

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?

  • Casey - time constraint Conference over the weekend.
  • Valerie - Mentor session on Thursday.
  • Courtney - Mentor session 5:30 Wednesday

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

  • Slack

  • Charlotte - (202) 531-3141

  • Courtney - (520) 262-1279

  • Valerie - (303) 881-6396

  • Casey - (781) 738-0071

  • Standups and Retros

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

  • Valerie / Casey - TDD
  • Charlotte / Casey - Authentication + Authorization
  • Courtney / Charlotte / Casey / Valerie - PORO's
  • Courtney / Casey - Styling + wireframing
  • Valerie - Schema planning
  • Valerie - NO STYLING

Strengths

  • Charlotte / Courtney - TDD
  • Valerie / Casey - Styling
  • Casey - Debugging
  • Courtney - Authorization Debugging
  • Casey - Schema planning

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

  • Finish project - all
  • All - Understanding cart life cycle
  • Rails helpers
  • Implementing user stories from instructors.
  • Casey - increasing communication throughout the process.

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?

  • Waffle.io
  • No merging own stuff into master
  • Dev branch
  • 2 approvals before merges
  • Thorough code reviews

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

  • Communicating and asking for help.
  • Timebox issues.

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

  • Code reviews
  • Retros and Standup

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

  • Bad at approaching problems collaborativly when understanding is flimsy
  • Check Valerie
  • Courtney - Take breaks
  • Sleep is important.
  • Go with the flow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment