Skip to content

Instantly share code, notes, and snippets.

@noetic97

noetic97/feedback_conversation_reflection_guidelines.md

Last active June 5, 2017 18:34
Show Gist options
  • Save noetic97/3aa2c4baddd3d9e35677c033b90a7159 to your computer and use it in GitHub Desktop.
Save noetic97/3aa2c4baddd3d9e35677c033b90a7159 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
feedback_conversation_reflection_guidelines.md

Feedback II Reflection

  1. Date of feedback conversation:
  • 05/10/2017
  1. How did you prepare for the conversation?
  • I worked through the project timeline to find areas where we could have improved our workflow. I realized that we could better communicate and write down the issues that we need to work through to keep us on track. This may have also allowed us to pivot from some of the biggest struggles that we faced along the way and move onto new feature sets more quickly. More regular commits on each new feature set would come out of better defining the issues list as well.
  1. How did the conversation go for you? What was easy about the conversation? What was more difficult?
  • The conversation with James was really fairly easy. We both agreed that we could make a stronger effort to define our project issues so we could break down the project into a more approachable set of smaller issues to solve. We commited to holding each other accountable.
  1. What principles of feedback did you use in the conversation?
  • We used the open-body-close principle. We started by clearly defining what we were going to talk about, then worked to stay on topic by keeping the opening narrowly scoped, then made sure that we had an action to come out of the feedback with.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment