Group Member Names: Dan Olson, Katy Farmer, Courtney Meyerhofer
Project Manager: Courtney Meyerhofer
- What is the project manager's role? How do we want the days to be scheduled? What do we want included in the daily schedule?
- Scheduling:
- Keep track of pairings
- summary of each day (accountability, cards)
- assign cards to members
- check in on cards that aren't moving
- Long-term Scheduling of project completion:
- understand spec in depth
- checking in on rubric
- updating group members on our progress, pacing
- reminders and summary posted in slack daily
- 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
- 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
- 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
- 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
- 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
- GitHub: work on our own branches, branch names have our initials in them, feature name, iteration name
- ping in Slack when PR up
- frequent PRs
- 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.
- 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
- 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