DTR Memo Project: Refactor Tractor
Group Member Names: Kim Cochran, Brian Roxbury, and Kyle Williams
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?):
Kim- Wants to practice using fetch. Possibly look into charts.js. Brian- Experience working on a part of all aspects of the project. Wants to design a workflow where everyone has their part in every element of the application. Kyle- Working on issues using GitHub, making them smaller and more manageable. Practice the review process built into pull requests.
Each person will be able to speak to every aspect of the code. We'll help eachother understand concepts that are in the project in order to do well in the assessment.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Kim- Has a good grasp on project as a whole. Has ideas on extensions and pushing further. Open to different roles. Hard to deviate from a projected path (that may or may not work). Brian- Easy-going, will take on roles as they are needed. Needs to think through things independently. Kyle- Needs time to think about problems on his own, but usually gets the tough stuff. Stubborn with over-engineering code.
Complete a brainstorm before starting the project. Heavy focus on classes (methods and organization) and consistency (variable naming, etc.) at the beginning. We can branch off more as time progresses.
How we can use our strengths to overcome obstacles: When we find ourselves going down the "one-track" road, we use the maximum 45 minute rule where we should step back and reconsider our approach. Enforce the use of poms.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Kim- Working on weekends isn't preferred. Max one half per weekend. Brian- Pretty open to work any time. Needs a little buffer each evening to be human. Kyle- Has dinner with his family at 5:00pm. Prefers to not work on weekends, one half-day per weekend.
All subject to change due to stress.
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'll be talking every day. Check in and state our daily goals/milestones. Slack and Tuple.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Kim- Glows: Familiar with the project already. Has ideas for extensions and making our project 💪. Grows: Refactoring, Sass, CSS, fetch Brian- Glows: DOM manipulation. Grows: jQuery, Spies, Sass, CSS, etc. Kyle- Glows: Classes. Grows: Practice using fetch, learning what Sass is.
Workload Expectations (What features do we each want to work on?): TBD
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Git workflow/Tools/Code, Review/Reviewing Pull Requests/Debugging, and Problem-solving Techniques.
Expectations for giving and receiving feedback: Assume positive intent. "When you do ______, I feel ______."
Project management tools we will use (GitHub projects or Trello are popular tools): Yes.