Skip to content

Instantly share code, notes, and snippets.

@hfaerber

hfaerber/DTR-project-3.md

Last active September 4, 2019 00:56
Show Gist options
  • Save hfaerber/31644260287a677a490788f60352ea60 to your computer and use it in GitHub Desktop.
Save hfaerber/31644260287a677a490788f60352ea60 to your computer and use it in GitHub Desktop.
Download ZIP
DTR - Group Project - Karen, John, Heather
Raw
DTR-project-3.md

DTR: Define the Relationship

Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.

Guiding Questions to Define The Relationship:

  • What are each of our learning goals for this project? What drives us in this project? -K: getting JS function down, specifically writing it, not just understanding it. -J: taking the time to psuedo-code and verbalize it before writing code. Getting confidence regarding event bubbling/targeting. -H: putting all the pieces together to build functionality more quickly and with smoother flow. Refactoring - when?

  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? -J: needs time to process first. Happy medium between pair/divide. -K: talk it out but be able to go home with your own tasks -H: happy medium. talking out in advance when the next steps are and prepping for them so pairing time is most effective

  • How do you communicate best? How do you appreciate receiving communication from others?

  • Direct and constant, proactive communication. Recognizing that when we aren't feeling understood and have to restate/be more assertive, its an uncomfortable place to be right off the bat.
  • How would you describe your work style?
  • K and H work a little slower and don't want to struggle to keep up. We think working together (even if we're doing out own thing) will be valuable. Communicating when we're feeling like we're on difference paces will help us come up with a solution together.

  • What are each of our strengths? How can our strengths complement each other? -J: planning out the work/timeframes, flexibilty, level-headed/calm -K: communication and flexibility -H: willingness, flexibility and being aware of if everyone's feeling good -Help each other take breaks, especially when someone's getting wiggly. -Force each other to prove we're up to speed by explaining the most recent progress.

  • What’s gone well or poorly in your previous projects? -Daily standup at 8:30am (merge the progress). << We will do this. -Keeping an eye on slack and communicating via DMs - set timeframes? or communicate sign-off -phone number share but only for calling (no texting) - recognize that we're not 100% available by slack or phone. -We will use github projects for proj management. -K and H want to pair with smart people on non-proj stuff. John is willing to pair with us too. -K: clarifying git and git hub processes

  • How will we set direction and make decisions as a team? -Dont go rogue. -Hear each person viewpoint then decided together. -Make sure your team knows what you're doing before you're doing it. Have a back up plan in place if you get done with the other thing.

  • How will we overcome obstacles? Daily standup: are you feeling heard? are you feeling caught up? what do you feel least confident explaning right now? Making sure our group knows whatever crunchy bits are happening in the group before taking it outside the group - using outside the group for resources and guidance not venting.

  • What do you need (resources, environment, communication) to do your best work?

  • we dont know our environment preferences, flexible. working AT Turing is good for productivity. J is very productive at home too (can get into the zone). Communication is most important (frequent)

  • What scheduling restraints do you have? What are your scheduling preferences? J is taking fri evening off. H too. Fri evening and Saturdays are the preferred days to take a break from it (J prefers Sat am/afternoon off and is cool to work sat evening)

  • What is your style for giving feedback? Does anything ever hold you back from giving feedback? -K requests we talk about it and not just take over if we feel like she's being slow. -J not super comfortable giving constructing feedback, not wanting to ruffle. -H harder to give constructive than positive

  • What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills? -pairing, driver-navigators, help each other google, helping each other recognize when and what to ask for questions

  • What tools do you want to use to manage the project? GH Projects

  • How do you want the group to solve problems when members run into issues with features of the project?

  • talk about it in daily standup. address it in the moment. setting a timer and deciding what will happen once time up like it or not. using resources/asking for help - mentors, rocks, classmates, eric/amy(think of them as project managers at a job).

  • How do you know if a project is successful? How can we achieve that as a group? OUR QUESTION >>How many iterations will we all be comfortable getting through? I haven't gotten through iteration 2 on anything yet really. I'd like to get further but we might be coming in with a big gap. :/ ^^have a good plan. communicate. having our own goals more frequently - be realistic. If our paces aren't aligned, split up to work individually and everyone gets however far they get but we pair up the next day and make sure everything we all did is explainable by each of us before moving forward.
    CURRENT END GOAL: Get through Iteration 3. K - write JS function on her own

  • How will we recognize each other's successes and celebrate them? High fives and thank you's. Dont let any tiny success for uncelebrated.

Any additional questions that you would like to add:

Template for DTR Memo

Project: Check Yo'Self

Group Member Names: Karen Nguyen, John Adams, Heather Faerber

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

CURRENT END GOAL: Get through Iteration 3.
K - write JS function on her own

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

-J: planning out the work/timeframes, flexibilty, level-headed/calm -K: communication and flexibility -H: willingness, flexibility and being aware of if everyone's feeling good

How we can use our strengths to overcome obstacles:
-Help each other take breaks, especially when someone's getting wiggly. -Force each other to prove we're up to speed by explaining the most recent progress.

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

  • J is taking fri evening off. H too.
  • Fri evening and Saturdays are the preferred days to take a break from it (J prefers Sat am/afternoon off and is cool to work sat evening)
  • Daily standup at 8:30am M-F
  • Commit to stay until 7pm (except this Friday - leave by 4:30 - 5pm - will make plan for what to do before Sunday)
  • This Sat: Not coming to Turing.
  • This Sun: We will come to Turing on Sunday. Meet here at noon until ?

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

  • Slack presence. If you can't reach someone on Slack, use phone number but call (leave vm), not text. Texting should be through Slack.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): K - writing javascipt. Implementing use of classes and objects. H - implementing paraments and SRP. Implementing use of classes and objects. J - taking the time to psuedo-code and verbalize it before writing code. Getting confidence regarding event bubbling/targeting. Implementing use of classes and objects.

Workload Expectations (What features do we each want to work on?):
H - some CSS K - CSS flow j - the CSS master We will touch base at daily standup to better divy features. We will pom every 45 mins to 1 hour.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Karen will own repo - J and H will be collaborators. Don't merge your own pull requests. Go through the process of looking through the pull request and commenting/asking questions/communicating on GH (not Slack). Commit message format > start with capital letter and verb . "this commit will ______" Touch base at daily standup on how often we're committing. 3 - 4 commits per Pull Request. The commits are the process even if not finished. The PR would be the finished bit. Each commit should be describable with a simple commit message.

Expectations for giving and receiving feedback:
-Specific, kind, honest, frequent. In person whenever possible - standups. Give time and space to digest if not positive feedback.

Project management tools we will use (GitHub projects or Trello are popular tools): GHP

Day 1 Agenda:

  • DTR Memo submission
  • Create GH project board
  • Create repo
  • Enable GH pages
  • Wireframe
  • Send all the above to PM in DM or Channel
  • Build out HTML (if time)

Additional Notes:

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