Skip to content
English
  • There are no suggestions because the search field is empty.

How-to: Run the Sprint Review/Planning Meeting

MEETING OBJECTIVES

This meeting is to give an overview of the sprint that is ending, have engineers demo some of our new features, allow other staff to ask questions about the new features, and then give an overview of what we will be working on in the new sprint.

PREPARATION

  • Navigate to the Sprint Review and Planning Meetings Document and select the link for the sprint that is ending (click the link on the subsequent page as well to get to the actual document)

  • Send a message in the Engineering & Product chat the day before the meeting to remind Engineers to update the Confluence document with their demos:

  • Look through the tickets listed for demo in the top filter to see if there is anything listed that isn’t necessary for demo

  • If needed, update the “Major completed items for discussion” section to reflect the correct version number and release dates (This step is done after the last meeting, but double check to make sure)

  • Review the “Major completed items for demo” to make sure that none of the demo tickets listed are from last month’s meeting

AGENDA

  1. Start the recording!

  2. Go over the information in the “Major completed items for discussion” section

    1. This is an overview of what sprint just ended, what release version we will be compiling, and give the tentative dates for the release of that version on the First Adopter and General Cloud Pods

    2. Release date information is available on the Product Release Schedule calendar

  3. Pass things over to the Engineers to demo their completed development tickets

    1. Look to the “Major completed items for demo” for the demo order

  4. Ask the attendees if anyone has any questions or feedback about the demos.

    1. After questions, you will be moving over to the Sprint Planning portion of the meeting

  5. Share your screen and show the XD Sprint Board

  6. Give an overview of what we have planned for the upcoming sprint

    1. Information about the sprint objectives are listed in the Action Menu>Edit Sprint option

    2.  

      If you are also running the sprints, then you will need to make sure that you fill that information out prior to the meeting.

    3. The Sprint Overview should list the following:

      1. Sprint date range

      2. The # of weeks the sprint will run (This is typically 4 weeks)

      3. Listed out major objectives/developments that we will be working on within the sprint

  7. Give an overview of where we are on the Product Roadmap

  8. Meeting End

POST MEETING ACTION ITEMS

  1. Add “SprintDemoComplete” label to all tickets that were demoed during the meeting

    1. You can right-click on the Jira issues link at the bottom of the ticket filter to do a bulk edit of the tickets

      1. Open the Jira Filter

      2. Select the 3-dot action menu and select the “Bulk Change” option

      3. On the Labels row, select the “Add to Existing” option and then enter in “SprintDemoComplete”

      4. Please make sure to not add the label to any tickets that did not get demoed

  2.  
     

    Create a new Confluence page for the next sprint meeting

    1. Go back to the main Sprint Review and Planning Meetings Document and click on the Sprint # that you just had the meeting for

    2. Click on the 3-dot action menu and select “Copy”

    3. On the “Copy” modal, enable the “Include 1 child” (referring to the child page) and then click the Next button

    4. Use the “Replace title word” and “With title word” fields to change the sprint number from the old number to the new number (See screenshot below)

    5. Click the Copy button and the next sprint’s page will be created

    6. Open the new page and update the info in the “Major completed items for discussion” and “Major completed items for demo” sections as needed

    7.