Skip to content

Instantly share code, notes, and snippets.

@case-eee
Forked from Carmer/retro_feedback.md
Last active November 10, 2016 18:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save case-eee/2251e141339eb9f8f02abee94d7ae332 to your computer and use it in GitHub Desktop.
Save case-eee/2251e141339eb9f8f02abee94d7ae332 to your computer and use it in GitHub Desktop.

Group Retro and Feedback

Retro

First, take about 20 minutes and do a retro about your group experience. What's a retro? Think about our friday whole module retro - positives, negatives, and so-sos and actionable things you can improve to better the situation for next time. Here is a short read that may help define retros if you need a little more context. It may be helpful to revisit your DTR conversation too.

Feedback

"By not giving me feedback, you're preventing me from growing." -Anonymous Student

Giving and receiving feedback is the core driving force behind personal and professional growth. We want to take time to give feedback every time we work in groups. Make sure your feedback for an individual is actionable, specific, and kind.

Here is an example of actional, specifc and kind feedback:

  • Casey you're strategy to aproach a new problem is inspiring, however I felt you moved quickly through implementing < insert specific thing here >.
  • Casey you attempted every suggestion form the group to ensure every voice was heard.

Today, give each of the members of your group one critical and one positive piece of feedback and make sure it's actionable, specific and kind. You can see the above example for once critical and one positive feeback example.

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