New Sprint Demo Process

Revised Jan 26, 2026.

1. Please post sprint demo slide decks (as .ppt/pptx files) to this FOLIO - Google Drive folder Sprint Reviews - Google DrivePreview . Only the most recent ppt should be in this folder.

   1. Each time you add a new slide deck, move the previous deck to the Old Sprint Demos folder.

   2. The file name should include the demoed sprint number(s) and team name and team main development area. 

      1. Sprint #_Team name_main_development area
         228-229_Volaris_Resource Access

2. Here is an example of a slide deck prepared for Spitfire. Please use this deck as a starting point and adjust for your team and/or demo needs.
   FOLIO-Spitfire-Sprint-Demo-Review.pptxPreview

1. Sprint Demo Recordings: Recordings must include audio and be an MP2 or MP4 format (.mpg file extension). These demos will be published to the Open Library Foundation channel and the viewers expect to hear the presenter. Captions need to be enabled. If you would like to be able to edit your captions, you can download Capcut or a similar video editor. If you use a different tool, please make sure to upload the subtitle/closed caption file with the demo recording video as described in step 4 below.

2. What to Include in a Sprint Demo Recording: What have you worked on in the last sprint or two? Demo and record it. Is it highly technical? Include it and make sure to explain the context. Is it a small bug with big impact? Demo and record it. Is it a large bug? Demo and record that. The goal is to share what we’re spending our time on, whether it’s feature level exciting, technical work that can be showed with postman, bugs, small enhancements, UI work, etc. What work do you want curious viewers to see?

3. Sprint Demo Recordings Frequency: The team decides on the cadence. If your team prefers to demo and record every sprint, great. If your team prefers every 2 sprints, that is great too. We hope every two sprints will be achievable.

4. Sharing Demo Recordings: There is a shared folder for these recordings. These recordings are stored with this folder structure: Sprint Demo Recordings > Main development area. The recording file name should include the demoed sprint number(s) and the team's name. Ideally the demoed sprint number(s) is the first part of the file name to make it easy to sort and thus load to YouTube. 

   1. Sprint #_Team name_main development area_demo
      228-229_Volaris_Resource Access_Demo

• Acquisitions 

• Bulk-edit 

• Consortia 

• Discovery 

• Electronic Resource Management 

• Metadata Management 

• Platform 

• Reporting and Lists

• Resource Access

• Resource Management 

• Resource Sharing

• Reporting and Lists 

• Serials

• User Management 

5. The channel manager (not you!) will upload all videos on the second Wednesday of each month. Each playlist will represent the sprints from the previous month. Demo recordings uploaded to the folder since the prior months posting to YouTube will be included.

6. This process is iterative so please share what you learn so we can continue to improve. 

The FOLIO Sprint Demo channel manager on the OLF YouTube Channel will be responsible for the following:

1. Each month, demo recordings uploaded here will be uploaded to the OLF YouTube Channel

2. A new playlist will be created for each month’s sprint(s) demos. The playlists will be named in the following pattern:

   1. FOLIO Sprint Demos: Month Year
      Example: FOLIO Sprint Demos: January 2026

3. All videos and slide decks will be uploaded to the playlist and will follow the naming in Step 4 above (Sprint #_Team name_main development area_demo).

4. A description will be included “Work completed in FOLIO Sprint # by team Name.” For example, Work completed in FOLIO Sprint 232 by team Spitfire.

5. YouTube autogenerated subtitles/captions will be enabled unless a file was uploaded with the demo video as described in Demo Recordings Step 1 above.

6. All videos will be scheduled to publish in the playlist on the same date and time.