Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 210 views

    Iteration Review Facilitator Checklist

    Uploaded by

    lyaviol
    The document provides a checklist for facilitating an iteration review. It includes steps to prepare such as updating iteration goals and testing the product increment. During the review, stories that were worked on should be demonstrated and feedback received. Following up, the team backlog should be updated based on feedback and work not completed identified to move to future iterations. Tips are provided such as limiting demo preparation time and ensuring the right participants are present.

    Copyright:

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

    Iteration Review Facilitator Checklist

    Uploaded by

    lyaviol
    210 views1 page
    The document provides a checklist for facilitating an iteration review. It includes steps to prepare such as updating iteration goals and testing the product increment. During the review, stories that were worked on should be demonstrated and feedback received. Following up, the team backlog should be updated based on feedback and work not completed identified to move to future iterations. Tips are provided such as limiting demo preparation time and ensuring the right participants are present.

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides a checklist for facilitating an iteration review. It includes steps to prepare such as updating iteration goals and testing the product increment. During the review, stories that were worked on should be demonstrated and feedback received. Following up, the team backlog should be updated based on feedback and work not completed identified to move to future iterations. Tips are provided such as limiting demo preparation time and ensuring the right participants are present.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    210 views1 page

    Iteration Review Facilitator Checklist

    Uploaded by

    lyaviol
    The document provides a checklist for facilitating an iteration review. It includes steps to prepare such as updating iteration goals and testing the product increment. During the review, stories that were worked on should be demonstrated and feedback received. Following up, the team backlog should be updated based on feedback and work not completed identified to move to future iterations. Tips are provided such as limiting demo preparation time and ensuring the right participants are present.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 1

    Iteration Review Facilitator Checklist

    Preparation Checklist
    Update the status of the Iteration goals
    † Make sure the time and location of the Iteration
    †
    review is known
    Product Increment is tested and ready to demo
    †
    Invite other stakeholders who will want to see the
    †
    Agree on the presenter and order of the stories to
    † team’s progress, which may include members
    be demonstrated
    of other teams
    Prepare any findings and results required to
    † Teleconference and/or videoconference line
    †
    demonstrate spikes and refactors
    is reserved and communicated in invitation for
    remote attendees

    Actions to take from Iteration Review


    Update the Team Backlog based on the feedback
    † Take these findings into the Iteration retrospective
    †
    of the Stories demoed and consider how the next Iterations can be better
    planned and executed
    Reflect on the unfinished stories
    †
    Identify work for integration in the cross-team
    †
    This often reveals impediments or risks, false
    † System Demo
    assumptions, changing priorities, estimating
    inaccuracies or over-commitment Move the work not completed to the backlog for
    †
    prioritization and consideration in future Iterations

    Tips and Techniques


    • Limit demo preparation to one to two hours • The Product Owner should not be seeing the
    • Ensure different team members have the stories demoed for the first time during the
    opportunity to demo Iteration Review
    • Minimize the use of slides and demonstrate • Make sure the right participants are present
    working product increments run from • Avoid the team becoming passive actors and the
    appropriate environments Product Owner doing all the talking
    • Incomplete work should not be demonstrated • The team discusses issues/risks uncovered during
    without proper caveats the Iteration and captures feedback
    • Progress towards the team’s PI • Ensure the team celebrates its accomplishments
    Objectives is discussed and stakeholders acknowledge them

    PROVIDED BY

    You might also like