Scribd Logo
Upload

Welcome to Scribd!

  • 5 views

    Mod 9

    Uploaded by

    bicool93

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Mod 9

    Uploaded by

    bicool93
    5 views15 pages

    Original Title

    mod 9

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    5 views15 pages

    Mod 9

    Uploaded by

    bicool93

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 15

    Agile Project Management

    MGMT-6061
    Module 9

    Sprint Retrospective
    Module 9

    Learning Outcomes
    Understand and explain Sprint Retrospective:
    • Participants
    • Prework
    • Insights and Actions
    • Sprint Retrospective Issues

    This slide presentation augments your Course and


    Module Readings. Complete the module readings
    before reading through this presentation.
    Retrieved June 18, 2013

    Scrum Framework
    http://www.informit.com/articles/article.aspx?
    p=1952809

    This is the last


    meeting/step in the
    framework
    The Sprint Cycle
    • Planning meeting the first day
    • Sprint execution every day of the sprint
    • Stand up meeting every day
    • Demo on the last day (The Sprint Review)
    • Retrospective
    The Sprint Retrospective
    • An important part of the Sprint process, but one that is not
    always appreciated
    • An inspect and adapt enabler for the team’s Scrum process
    • Based on principles of Continuous Improvement, a foundational
    element to quality
    • Agile projects have many unknowns, the Retrospective is the
    opportunity to perform course corrections along the way
    Participants
    • The entire team should participate:
    • The ScrumMaster
    • The Development Team
    • The Product Owner
    • If there are issues with the team being “open” with the
    PO in attendance, the situation has to be resolved
    over time
    • Stakeholders and Managers should only attend if
    invited (one-off meetings)
    Prework
    • The focus is on how the steps in the Sprint process
    worked
    • Ad hoc areas of focus may be applicable, e.g. new
    training requirements
    • The focus may suggest additional participants
    • The choice of focus and participants drives:
    • The selection of reflective team exercises
    • Objective data to be gathered
    • How the retrospective meetings and activities should be run
    Video
    The Wrong way to do Agile: Retrospectives

    1:13

    https://www.youtube.com/watch?v=FJezcyKno5k
    Retrospective Activities
    • Big picture questions are:
    • What worked well that we should keep doing?
    • What didn’t work well that we should stop?
    • What should we improve or start doing?
    • An open process without retribution
    • Any team feedback process needs a high level of trust for open
    communication
    • Team members won’t participate if trust isn’t there
    • The process involves sharing differences of opinions
    • There is both objective and subjective information, both are
    valuable
    Insights and Actions
    • The team analyzes data and subjective information
    • The intent is to apply insights at a systems-level first (the overall
    process)
    • Answering the big picture questions will drive insight:
    • What worked well that we should keep doing?
    • What didn’t work well that we should stop?
    • What should we improve or start doing?
    • There may be more insights and opportunities to improve then
    can be done
    • Specific improvement actions are selected
    Sprint Retrospective Issues
    • If the team does not “follow through” with actions
    coming out of the Retrospective, the Retrospective
    will become low or of no value
    • An open and trusting environment is required
    • Continuous Improvement usually yields dramatic
    results over time, rather than via a one-time event
    • Feedback can be emotional, or discouraging, or a
    complaint session
    Video - 7 Deadly Sins
    Agile and the Seven Deadly Sins of Project
    Management

    https://www.youtube.com/watch?v=U41uxRtjdLI
    Other Module Activities
    • Ensure your perform all the module
    activities such as Dropboxes,
    Discussion Threads, group work,
    research – and the readings
    Module 9

    End of Module
    Parts of this document were sourced from:

    Essential Scrum - A Practical Guide to the Most Popular Agile Process


    Author: Kenneth S. Rubin
    Publisher: Pearson Education, Inc

    You might also like