Sprint End Activities

At the end of each sprint the Engineering Manager and Program Team will review the progress of the sprint as follows:

• Program Sprint Review
• Engineering Managers will send Sprint Complete Email to the Operations Information R&D organization
• The Program Manager will post the video of the Program Sprint Review
• MS Teams Location OSIsoft Engineering -> Program Sprint Reviews channel
• Include a brief description
• Include a sprint date
• Include the program name
• Include a link to the recording from MS Streams- All R&D should be able to see it.

Program Sprint Reviews

The Program Sprint Review is organized by the Program Manager but is executed by the Engineering Managers and teams. The goal of the Program Sprint Review is to demo the work completed in the sprint. The review should be structured so that the features completed in a sprint are demoed by the developers that completed the work. In the event there are no demos, the Program Manager may decide that there will be no sprint review for this period, but the Engineering Managers must still complete the sprint end tasks.

Demos

The demo should contain an overview of the feature, why we're building it then show how to use it from the user persona's perspective. Developers should demonstrate that they understand why we're building any particular feature. If we are demoing part of a larger feature story, the developers should explain what aspect of the larger story they are demoing.

Demo Tips

• Show only done work
• Avoid slides where possible, use slides to add color to the demos, i.e. picture of workflow, architecture etc.
• Avoid the technical details, focus on the outcome
• Avoid "what's next" content
• Focus on End to End demos, not pieces and parts of a larger feature
• Avoid showing demos from your develoment machine, show done deployed features

Reporting Team Progress

It is not necessary to review the teams story point completion, list of WI's completed or impediments during the sprint review. That will be reviewed during the Scrum of Scrums and Program Sprint Planning sessions.