Skip to content

Latest commit

 

History

History
52 lines (38 loc) · 2.39 KB

DTR.md

File metadata and controls

52 lines (38 loc) · 2.39 KB
Raw

Project: Chez Produce

Group Member Names: Erin King, Jalena Taylor, Jennica Stiehl, Smitha Hosmani

Team Name: She-que

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?):

  • We recognize each of us has our own unique strength and unique area to improve.
  • We would like to collaboratively work togther to achieve our goals.
  • We each wish to prioritize learning.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

  • Balance of pairing and divide and conquer.

  • We all have great communication skills - open, honest and respetful.

  • We have a good balance in the group - power to perservere and the power to take a POM.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

  • The group will be available to work together at school until 6pm.
  • Stand-Ups will be at 8:30am.
  • Independent work/study-time will take place outside of scheduled project work time.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

  • We will revisit DTR on Tuesday, 4/2/19 to gauge group dynamics and processes.
  • We will decide if we need to revisit and DTR the following week on Tuesday.
  • We will summarize our stand-ups on Slack.
  • Communication will be in person and via Slack.
  • Individuals who might miss stand-up will send a summary of what they would have shared via Slack on group's channel.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

  • Learning material and advocating for ourselves on topics we would like to learn more about.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

  • Never merge our own PR.
  • The person merging will refer to the relevant user story to ensure completion of user story requirements.
  • TDD
  • Helpful bite sized commit messages and detailed PR messages.

Expectations for giving and receiving feedback:

  • Using a template for stand-ups.

Project management tools we will use: GitHub

Day 1 Agenda:

  • set up co-author
  • read thru user stories together and hash out ideas for database design and wireframes.
  • decide who will work on which wireframes.
  • Rails new.
  • stand-up at the end.