/
Return of the community system demos

Return of the community system demos

Background

During the early period of FOLIO, we held community system demos. These demos allowed developments teams to showcase the work they did for 1-2 sprints. It allowed the community the opportunity to see development in progress and comment.

FOLIO develops new functionality at a tremendous pace that is very hard for users to keep track. As a result, it is hard for FOLIO institutions to know what/when features will be available. Thus the need to return to community system demos.

Lets do community system demos in a different way

Previously community system demos were 90-120 minutes. These monthly meetings were live and attendees were limited to development teams. With the return of these demos, we want to ensure they are inclusive to the entire community to know what development teams are working and to provide feedback.

New Sprint Demo Process

  • https://folio-org.atlassian.net/wiki/spaces/PO/pages/1484062753 - We will ask teams to present the work they complete for one or several sprints so that the community may view work much earlier in the development process. Teams will record their demos and these demos will be posted to the OLF YouTube channel for the community to review.

Questions

  1. My team has a demo every sprint, must we do a monthly demo? No. Whatever is easiest for your team but teams must complete the template.

  2. Can my team have live system demos with the community and still make it available as recording? Yes, it is whatever your team prefers. If you prefer live great but we know this might be difficult as a team might not be available at the time folks can attend. The demo must be recorded.

  3. What if my team has nothing to demo? These demos will be held every 1-2 sprints, if your team has nothing to demonstrate, please post your system demo communication so that the community is aware of progress.

  4. What is the typical duration of these demos? If per team then ~15 minutes.

  5. Can our team use the MQA recordings only? The demo must have audio of someone walking through the work.

  6. Could we work with a SIG on the effort? Yes, possibly the SIG could help with organizing a demo across multiple teams for a given track. They can also report back to the SIG, PC, and other groups a summary of the system demo(s).

  7. I have a question about the functionality that I saw demoed. Who do I ask? Each demo will have contact information and a list of the issues that will be demoed, you can send a message to the PO or SIG via Slack OR you can add a comment to the JIRA.

  8. I have a question why a team is working on a feature that does not seem to be a high priority. Please contact the PO/SIG with such questions. These demos are not meant to review feature priorities. They are meant to show progress on development in an iterative way.

  9. How can we leverage AI? TBD how to integrate to ensure an efficient workflow.