Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Continuous Feedback

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Continuous Feedback

Avatar for Chris Blackburn

Chris Blackburn

April 11, 2016
Tweet

Other Decks in Business

Transcript

  1. • Bias towards the last couple of weeks • Infrequent

    course corrections • No regular vent for unhappiness / dissatisfaction • Big time investment to run • Infrequent ‘deadlines’ for actions • People have little ownership over their feedback
  2. • Every 2 weeks or less, thou must have a

    Continuous Feedback session • You may ask anyone else in the team to compere your CF session • You are responsible for collating your own feedback
  3. • Both parties bring feedback to the session • The

    session is lead by the individual receiving feedback • Sessions typically last about 20 minutes
  4. • Some people are all over this • People are

    not always comfortable in giving ‘frank’ feedback • Not a good forum for larger course corrections • Need to figure out how to feed your company objectives in