Project: Linked Lists
Group Member Names: Thomas Laird - Maria St. Louis-Sanchez
Project Expectations: What does each group member hope to get out of this project? Making sure we're both understanding all the technical concepts that go into the creation of our project. Solidifying HTML, CSS, Javascript and jQuery concepts. Learn how to be an effective group for a project of this type.
Goals and expectations: Good communication throughout the project about availability. Produce a very good end product by evaluations. Finishing up through three phases if not all four. Meeting the specifications of the comp to a high degree of accuracy. Learning best practices vs. just building a working product. CSS and JS refactoring as time allows.
Team strengths: Maria - Good design, effective communication and good understanding of javascript. Thomas - Javascript, effective communication and very time flexible.
How to overcome obstacles: Acknowledging problems when we have them. Working through a solution where both team members compromise thoughtfully. Seeking mediation if necessary. Being respectful.
Schedule Expectations (When are we available to work together and individually?): Touch base after class when possible. Touching base in the evening. Lunches if needed, pairings during lunch as well. Getting off to a fast start. Being aware of when somebody's NOT available.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): A couple times a day during the week, several times over the weekend. Use slack during the evenings and in person during the day. Letting each other know if problems arise or if we need help with something as opposed to trying to grind it out ourselves.
Abilities Expectations (Technical strengths and areas for desired improvement): Thomas - Strength: Javascript Weakness: CSS, jQuery Maria - Strength: HTML & CSS Weakness: Javascript, jQuery
Workload Expectations (What features do we each want to work on?): Doing some driver navigator coding so that we can learn from each other. Not dividing CSS/JS up straight down the line.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Building lots of branches seperately and pushing/pulling from github frequently.
Expectations for giving and receiving feedback: Touching base frequently when features are done so that we can make sure they're up to both of our standards before moving on to the next feature set.
Agenda to discuss project launch: Divide early stages of project to get the easier parts of the project done. Meet frequently as the project goes along to work on the more challenging parts.
Ideas: Use slack to stay organized and in touch even on off-site hours. Maintain honest communication if one person or the other is feeling uncertain about a path being taken. Seek out help on features as necessary.
Tools: Trello - For organizing roles and features Git - version control Github - collaboration on files Slack - communication, screensharing. Sublime text
Additional Notes: