Agile2014

Do you often find yourself struck with a sense of déjà vu in the retrospective meeting at the end of a sprint? Do you spend your time arguing about things to START, STOP or CONTINUE every single time? Perhaps you feel like you are just highlighting the same old problems, which never get fixed? Has the team rebelled completely and decided that retrospective meetings are a waste of time?



The drive to inspect and adapt is one of the most important aspects of agile software development. A great way to bake this approach into your process is by having regular retrospective meetings that engage and challenge the team to solve their own problems and make things better. However, these meetings can be difficult to run well and drive improvement. In fact, many teams sleepwalk through sessions, treating them as a box-ticking exercise that signals the end of the iteration.



Maybe it’s time we tried a bit harder to make sprint retrospective meetings work?



In this workshop, Chris and Paul will explain exactly how to put together an awesome sprint retrospective. Attendees will try novel activities that can be used to gather information and challenge team members to consider problems from a new angle. They should leave the session equipped with new techniques to apply at the end of their very next iteration.