Template for DTR Memo Project:
Group Member Names: Phil DeFraties, Ryan Barnett, Dan Halverson, Daniel Lessenden
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
Try to stay ahead of schedule with user stories so that there will be space for preparing for presentation before due date. Make sure each team member gets experienced with every aspect of project requirements. Make usability of pages more intuitive/clear. Learn authentication inside and out.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Ryan - team authority on project management tool (github projects). Daniel - Grit/dedication/handsome. Dan - Big-picture, team organization, planning. Phil - research and implementation of unfamiliar tools/techniques.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
Daily meeting to plan story assignments, difficulty, pairing: @ 8:40am For daily meetings: 1. what have you accomplished 2. what are your plans for the day.
Dan - flexible depending on day, full lunch Phil - flexible depending on day, full lunch, screens off by 1030 unless behind schedule Daniel - takes walk in evening 1 hour, flexible, work through 1130ish pm Ryan - take evening walk, generally flexible
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
Slack as primary communication tool, any big problems with project make a github issue. Try to respond to messages in a timely manner. Every opinion must be heard and taken into account for decision making process, make sure everyone is on same page with understanding. Keep DTR open for edits/additions.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Improve on use and understanding of Active Record. Learn authentication. Refine HTML and CSS skills. Refine understanding of relationships between tables. Skinny controllers.
Workload Expectations (What features do we each want to work on?):
Stay on track with Timeframe, try to get ahead of schedule if possible. Make sure everyone has opportunity to get practice with each concept/skill. Advocate for yourselves. Plan out during daily meetings.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
New branch for each user story. Keep pr's small. Break up user stories into seperate pr's if story is difficulut/complex.
Stories will be rated on difficulty 1-5, 1's 2's 3's will have pr's reviewed by at least one person, 4's and 5's will need to be reviewed by entire team before merge.
Pomodoro Break Schedule:
As needed.
Expectations for giving and receiving feedback:
Be kind, be constructive. Dont be Mike.
Additional Remote Considerations:
Be open to driver/navigation pairing.
Project management tools we will use (GitHub projects or Trello are popular tools):
Github Projects
Day 1 Agenda:
Fill out DTR. Start adding user stories to GH Projects. Fork repo.
Additional Notes: