Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save blackknight75/86c6c0cbcf682a102d085ed9fba1a8d4 to your computer and use it in GitHub Desktop.
Save blackknight75/86c6c0cbcf682a102d085ed9fba1a8d4 to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Dan Olson, Katy Farmer, Courtney Meyerhofer

Project Manager:

  1. What is the project manager's role?

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

  • Dan: 10-12 peak work time during the week. Weekends are flexible but has frequent obligations that might break up work time.
  • Katy: short break at 4, after school until 7 in person (researching alone at night) --flexible
  • Courtney: available until 9 in person --flexible
  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
  • Dan: in person, 2 daily retros(planning & check-ins), slack checkins thoughout the day (quick). Communicate when making PRs and feature implementation.
  • Katy: in person preference, via our Slack channel, daily retros (2 morning & evening)
  • Courtney: in person, Slack (especially GitHub), daily retros
  1. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
  • Dan: MVC setups/file structure, routes, database queries and show pages, CSV integration. (extension (Google Maps)(OPTIONAL))
  • Katy: NO CSVs, RSpec, database relationships
  • Courtney: ActiveRecord and testing with RSpec
  1. What does each group member hope to get out of the project?
  • Dan: Database relationships(foreign keys and queries). Routes and VERBS. Data manipulation in the database. Improved understanding of raw SQL commands.
  • Katy: really firm understanding of MVC
  • Courtney: MVC, grow in pairing
  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?
  • PM tool: waffle.io
  • GitHub: 2 views and comments before being merged-- specific comments
  • ping in Slack when PR up
  • frequent PRs
  1. What is expected of group members when they run into problems implementing a feature?
  • set a time limit (30 mins) for when to reach out for help to other members or resources. If error can't be solved reach out to external resources for coaching.
  1. How does each group member want feedback (both positive and constructive) to be delivered?
  • Dan: Straight forward and in person(DM ok)/retros
  • Katy: in person, verbally
  • Courtney: during daily retros in person & sooner rather than later
  1. Is there anything else the group should know about personal work/communication styles?
  • Dan: Visual learner. Draws diagrams to understand relationships. Forced breaks. Teaching back what you learn/know!(VERY important to me both ways)
  • Katy: stop being able to see forest for trees, step back & need breaks, write down problem, form thoughts while talking
  • Courtney: be told to breaks, some alone time to work if not had a chance to process
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment