Scribd Logo
Upload

Welcome to Scribd!

  • 91 views

    82 - Fun Retrospectives - Agile Cambridge 2018

    Uploaded by

    murphy
    This document discusses retrospectives in Agile development. It defines a retrospective as a meeting at the end of a sprint or release to inspect what went well and identify improvements. The document outlines common retrospective techniques like "Glad, Mad, Sad" and provides examples like "The Starfish" and "The Flying Kite." It emphasizes that retrospectives aim to continuously improve the team through inspection and adaptation.

    Copyright:

    © All Rights Reserved

    82 - Fun Retrospectives - Agile Cambridge 2018

    Uploaded by

    murphy
    91 views16 pages
    This document discusses retrospectives in Agile development. It defines a retrospective as a meeting at the end of a sprint or release to inspect what went well and identify improvements. The document outlines common retrospective techniques like "Glad, Mad, Sad" and provides examples like "The Starfish" and "The Flying Kite." It emphasizes that retrospectives aim to continuously improve the team through inspection and adaptation.

    Original Description:

    82_Fun Retrospectives - Agile Cambridge 2018

    Original Title

    82_Fun Retrospectives - Agile Cambridge 2018

    Copyright

    © © All Rights Reserved

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses retrospectives in Agile development. It defines a retrospective as a meeting at the end of a sprint or release to inspect what went well and identify improvements. The document outlines common retrospective techniques like "Glad, Mad, Sad" and provides examples like "The Starfish" and "The Flying Kite." It emphasizes that retrospectives aim to continuously improve the team through inspection and adaptation.

    Copyright:

    © All Rights Reserved
    91 views16 pages

    82 - Fun Retrospectives - Agile Cambridge 2018

    Uploaded by

    murphy
    This document discusses retrospectives in Agile development. It defines a retrospective as a meeting at the end of a sprint or release to inspect what went well and identify improvements. The document outlines common retrospective techniques like "Glad, Mad, Sad" and provides examples like "The Starfish" and "The Flying Kite." It emphasizes that retrospectives aim to continuously improve the team through inspection and adaptation.

    Copyright:

    © All Rights Reserved
    of 16

    FUN RETROSPECTIVES!

    @agileamigo| Sriharsha (Sri)


    Sriharsha (Sri) | @agileamigo

    INTRODUCTION
    • A Father
    • A Loving & a Caring Husband “hopefully”
    • Sr. Scrum Master / Agile Coach @ Wipro
    • Co-founder of APGI - Agile Practioners’ Group
    of India
    • An Enthusiast Agile Blogger
    (www.agileamigo.com)
    • A Volunteer with Scrum Alliance
    • A Theatre Enthusiast
    Sriharsha (Sri) | @agileamigo

    Snow Storm
    Elementary meetings!

    • Bringing people together


    • Instant recognition
    • Enjoy
    • Display appropriate behaviour
    • Powerful
    Sriharsha (Sri) | @agileamigo

    Retrospectives- Definition & Purpose


    The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a
    plan for improvements to be enacted during the next Sprint.

    • Inspect how the last Sprint went with regards to people, relationships, process, and tools;
    • Identify and order the major items that went well and potential improvements; and,
    • Create a plan for implementing improvements to the way the Scrum Team does its work

    “…special meetings that take place at the end of a period of work—usually an iteration or software release” – Esther Derby
    Sriharsha (Sri) | @agileamigo

    An Anatomy of a Retrospective
    • Set the Stage (approx 10 mins)
    (Establish Focus, Share the plan, working agreements etc.)

    • Gather Data (approx 20 mins)


    (Create a pool of data, talk facts, and revisit the objectives)

    • Generate Insights (approx 15 mins)


    (Determine the root cause, observe patterns and build awareness)

    • Decide What to do (approx 10 mins)


    (Discuss around the actions, focus on 1 or 2 actions)

    • Close the Retrospective (5 mins)


    (Re-iterate all the actions, appreciate contributions and retro the retro.)
    Different Recipes of the Same Dish!
    Glad Mad & Sad
    The Starfish
    The Flying Kite
    Sriharsha (Sri) | @agileamigo

    The Elephant and The Mouse


    Sriharsha (Sri) | @agileamigo

    The Sailing Boat


    Sriharsha (Sri) | @agileamigo

    That Guy – This Guy


    Sriharsha (Sri) | @agileamigo

    Let’s Retrospect – Agile Cambridge 2018!


    Sriharsha (Sri) | @agileamigo

    After all…..
    Retrospectives are aimed at:

    • Inspect and adapt


    • Continuously improve
    • Think creative
    • Keep teams happy & motivated

    & remember:

    “We do not stop playing because we grow old, we grow old because we stop playing”
    (Quote courtesy: Ducan C & John C)
    Sriharsha (Sri) | @agileamigo

    References & Credits


    • Agile Retrospectives: Making Good Teams Great (Derby and Larsen)
    • Retrospective images courtesy: Deepika B- Wipro Technologies
    • Title and other images courtesy: Dhruv
    • Inspired by Belinda Waldock’s Retrospective workshop
    • http://www.funretrospectives.com
    • Scrumalliance.org/blogs
    • Snow Storm - Eric de Groot - https://tedx.frl/
    • https://www.slideshare.net/chris_smith1976/the-art-of-the-retrospective/5
    • https://www.dreamstime.com/namaste-vector-hand-drawn-symbol-yoga-design-
    image112101574
    • My all time motivation – Pooja 
    Thank You!
    www.agileamigo.com | @agileamigo

    You might also like