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

Agile Retrospectives

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

Agile Retrospectives

Talk for Tech Nottingham on what a retrospective is, why and how, ahead of running Tech Nottingham's annual retro session

Avatar for Andrew Seward

Andrew Seward

August 03, 2015

Other Decks in Technology

Transcript

  1. R E T R O S P E C T

    I V E S A N O V E R V I E W O F
  2. T O N I G H T W E W

    I L L C O V E R • What is a Retrospective? • Why? • How dis? • Tips for an effective retro • Do one
  3. W H AT I S A R E T R

    O S P E C T I V E ?
  4. W H AT I S A R E T R

    O S P E C T I V E ? • Discussion of what went well, what didn’t, and why • Structured approach to the continuous improvement of your processes • The most important part of the Agile process
  5. W H Y R E F L E C T

    A N D I M P R O V E ?
  6. W H Y ? • We accept that we know

    more about something the more we do it • We accept that we learn from our mistakes • We accept the people based placed to improve a process are the people that are involved in it
  7. W H Y ? • Continuously improve • Respond to

    change • Take ownership of improvement • Be more effective and happier • No more “I can’t understand why we don’t just....”
  8. D O W N T O O L S •

    The team stops what they are doing & gets together • Nominated facilitator runs the retro • Chooses format • Keeps time • Keeps people on topic
  9. R E F L E C T, D I S

    C U S S , A C T • Review previous actions • Review what you’ve done • Highlight successes and failures • Focus on the biggest issues • Discuss each one • Generate actions for improvement
  10. T I P S F O R A N E

    F F E C T I V E R E T R O
  11. T I P S F O R A N E

    F F E C T I V E R E T R O • Keep to the schedule • Limit discussion items and actions • Run retros regularly & dependably • Follow up on previous actions • Retroing is a skill and an exercise in trust - you’ll get better
  12. P R E V I O U S A C

    T I O N S • Improve microphone quality • Provide some food • More balanced mix of coding and people & practices
  13. W H AT H AV E W E D O

    N E S I N C E T H E L A S T R E T R O ? • Moved to Antenna • Rebranded as Tech Nottingham • Run Hack24 • Sessions: • JULY 2015 - LET'S PROGRAM A ROBOT WAR • JUNE 2015 - JAM PACKED! • MAY 2015 - REDIS IS THE ANSWER, WHAT'S THE QUESTION? • APRIL 2015 - AGILE PROJECTS: COMMON AND UNCOMMON SENSE • MARCH 2015 - CODING DOJOS FOR SMARTER TEAMS • FEBRUARY 2015 - CODE AT HOME AND IN THE COMMUNITY • JANUARY 2015 - CRAFTING INTERACTIVITY WITH ARTCODES • DECEMBER 2014 - DEVELOPING WITH THE OCULUS RIFT AND UNITY • NOVEMBER 2014 - CONTINUOUS DELIVERY AS A SERVICE • OCTOBER 2014 - SCALING TEAMS & JURASSIC PARK: WHAT WENT WRONG? • SEPTEMBER 2014 - THE LIMITS OF TELL DON'T ASK • AUGUST 2014 - MATT RELF, JENNI BROWN & JEREMY PARSONS