Skip to content

Instantly share code, notes, and snippets.

@leighlars
Created April 6, 2020 22:09
Show Gist options
  • Save leighlars/1ee79412b6200150637f773c6b569d64 to your computer and use it in GitHub Desktop.
Save leighlars/1ee79412b6200150637f773c6b569d64 to your computer and use it in GitHub Desktop.
Project: IdeaBox Group Project
Group Member Names: Dustin LaDue, Leigh Larson, Derek Romero
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?):
Demonstrate comprehension and skill of CSS & HTML. Adhere to comp specs as closely as possible. Clean and tight iterations rather then quantity completion. Understanding of JS functionality of completed iterations. Seek PR / reviews from mentors for insight. DRY and refactored.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Derek is cooperative, practical, maverick, courageous. Dustin is flexible / adaptable, cooperative, agreeable. Leigh is a maverick, pragmatic, approachable, flexible.
How we can use our strengths to overcome obstacles:
Be mindful of tone, but clear in message. Upfront, tactfully. Recognize it's about the team. Humility.
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):
1-4 TWTH, break 4-5, 5-??. Driver/navigator for all iterations. Alternate who's driving/committing multiple times a day. 3 min huddle prior to coding to plan what's being coded for each commit.
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?):
We'll be group slack calling daily, for multiple hours. Update schedule changes ahead of time. Slack anytime.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Dustin- Solid on attitude, work ethic. not strong on technical but my god, will I keep us going emotionally.
Derek- Solid on organization. structured, clean. JS is not strong point, but I do like CSS / design and am excited about this aspect of project.
Leigh- Solid on pragmatism, JS, but not solid on CSS / HTML but has reviewed enough to hang.
Workload Expectations (What features do we each want to work on?):
Dustin - Building a foundation in everything. CSS.
Derek - A little bit of everything. CSS.
Leigh - Same. Most excited about JS.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Frequent small commits, PR/code reviews from 3 mentors, walking through it together. Before commits, we do style / debugging review. Before final submission, we get an outsider's review on aesthetics.
Pomodoro Break Schedule: 50 min on / 10 min off. Whoever is not driving can keep track of time. Hour break after 4pm.
Expectations for giving and receiving feedback:
On the spot. Open-minded, available. It's not personal. Assume positive intent first. Tactful. Frequent.
Additional Remote Considerations:
Solid internet connection.
Project management tools we will use (GitHub projects or Trello are popular tools):
Github projects.
Day 1 Agenda:
Set-up. Read through spec, rubric, and README. Plan HTML, CSS using either screenshot mark up tool, or drawing it out ourselves.
Additional Notes: excited to crush it!!!!!!
@leighlars
Copy link
Author

Retro 1 Changes to DTR:

  • Timeline: Iteration 1 comp'd by Friday night 4/10.
  • Behavioral changes: Leigh asks to be called out on being too intense ("Hey slow down!"); Derek wants to be more engaged (talkative, responsible for tasks); Dustin wants to be pro-active in reaching out for help, expanding his resource network.
  • Approach strategy: group work, if struggling get on group call with mentor, review every code block before submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment