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
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
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
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
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