retro_feedback.md

Group Retro and Feedback

Retro

First, take about 30+ 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.

Glows -

• We finished!
• Our Gitflow was great!
• Team Lunch at Anthony's! We really got to know each other a bit more and talked about things other than Turing and Coding.
• Code looks really clean
• Communication was good
• Time/Schedule worked out really well - people showed up when they committed to showing up - no one was late or straggled behind
• We really stuck to our DTR
• Susi only had one small panic attack :)
• On Sunday we hit the Performing section of team building :)

Grows -

• Bryan missed his bus once :(
• We spent ALL weekend in the basement.
• Saturday was our storming day - there was some fear setting in about finishing, about understanding.
• There was some disconnect in learning styles - some people liked to do trial and error whereas others preferred a more think-it-through before we code style.
• we all got frustrated at different points

Actions

• Let's guess and check and do that trial and error but first state the anticipated result.
• in the DTR for next time, maybe brainstorm a few ways to handle frustration. This way we can have a plan created while team members are calm that can be implemented when needed.