00:15:56	Khalilah (EBSCO):	https://folio-org.atlassian.net/wiki/spaces/PO/pages/1252393139/Return+of+the+community+system+demos
00:20:29	Steph Buck (EBSCO):	A way to share without eating two hours of our time is a great path forward
00:21:00	Christine Schultz (EBSCO):	Is the expectation that the devs themselves would be responsible for recording the demos each month?
00:22:17	Charlotte Whitt:	Yes, presentations for the SIG is also how I have done it with my teams
00:29:26	Khalilah (EBSCO):	We have the release digest. Does that help in giving the update that Owen mentioned?
00:31:16	Dennis Bridges:	I agree with that I just have a hard time believe people are going to watch the content. I think it would be better for this to be a monthly update in bullet form. That if people see something in those bullets they MIGHT watch a recording related to that bullet.
00:31:36	Alvaro:	Reacted to "I agree with that I ..." with 👍
00:31:41	Joe Reimers (EBSCO):	I think there's a basic difference between a feature review and a sprint demo, so I think we need to be clear on that.
00:32:03	Charlotte Whitt:	Reacted to "I think there's a ba..." with 👍
00:32:26	Dennis Bridges:	100%
00:32:49	Charlotte Whitt:	But every sprint - there will not (always) - be something to demo
00:33:25	Joe Reimers (EBSCO):	Showing an API payload in Postman as a result of sprint work is something that can be demoed
00:34:25	Christine Schultz (EBSCO):	Replying to "Is the expectation t..."

I guess my question is more related to the idea of audience. With multiple demos already occurring, I'm just wondering about the level of detail and who it's for. I'm struggling to understand if a sprint demo is the right content to go to a youtube video.
00:34:31	Christine Schultz (EBSCO):	Reacted to "I agree with that I ..." with 👍
00:35:31	Christine Schultz (EBSCO):	Reacted to "I think there's a ba..." with 👍
00:36:30	Steph Buck (EBSCO):	Reacted to "Showing an API paylo..." with 👍🏻
00:36:31	Ryan Taylor:	Reacted to "I guess my question ..." with 👍
00:36:33	Owen Stephens:	I should admit that we don’t do sprint demos.  But I think the regular ‘developer updates’ we do in the SIG is a reasonable substitute
00:36:37	Steph Buck (EBSCO):	Reacted to "I guess my question ..." with 👍
00:36:49	Owen Stephens:	Replying to "I should admit that ..."

Maybe we should start 🙂
00:37:28	Joe Reimers (EBSCO):	My bigger question is whether YouTube is the appropriate forum
00:37:32	Khalilah (EBSCO):	I see no different than the recorded system demos of the past, just broken up.
00:37:50	Joe Reimers (EBSCO):	Reacted to "I guess my question ..." with 👍
00:37:58	Christine Schultz (EBSCO):	Reacted to "My bigger question i..." with 👍
00:38:05	Charlotte Whitt:	Exactly: What is the audience we do demo for
00:38:53	Charlotte Whitt:	Release Digest is that intended for Stakeholders or for libraries using FOLIO?
00:39:22	Owen Stephens:	Replying to "Release Digest is th..."

Aren’t the libraries using FOLIO stakeholders?
00:39:31	Khalilah (EBSCO):	Replying to "Release Digest is th..."

Yes
00:39:51	Owen Stephens:	Replying to "Release Digest is th..."

I thought they were aimed at users of the system
00:40:19	Charlotte Whitt:	Replying to "Release Digest is th..."

Long lists of jira tickets - that’s not really user friendly
00:41:22	Charlotte Whitt:	Replying to "Release Digest is th..."

https://folio-org.atlassian.net/wiki/spaces/REL/pages/913506305/Ramsoms+R2+2024+Release+Digest#PDF
00:41:45	Owen Stephens:	Replying to "Release Digest is th..."

I think it’s hard to find the right way of summarising all of the features/changes in a release. I think using JIRA tickets as a structure is not a bad approach although I agree not perfect
00:43:45	Dennis Bridges:	“What is the audience” is the challenge. DO we need to do demos for each stakeholder? We already generate content catered towards all of these stakeholders. If stakeholders still don’t feel they have the information I think we need to focus on the distribution of the content we already produce rather than creating more content.
00:43:55	Christine Schultz (EBSCO):	Reacted to "“What is the audienc..." with 💯
00:44:00	Ryan Taylor:	Reacted to "“What is the audienc..." with 💯
00:45:00	Owen Stephens:	Reacted to "“What is the audienc..." with 💯
00:45:46	Dennis Bridges:	That is why I’m ok with the sprint demo but ONLY if it is a re-packaging of the demos we already do.
00:46:09	Thomas Trutt:	Brb — sorry
00:46:17	Christine Schultz (EBSCO):	Reacted to "That is why I’m ok w..." with ➕
00:47:16	Dennis Bridges:	I don’t think enough people will consume the demos to justify lets say 10 teams of 5 people each putting an additional hour into producing another demo.
00:47:18	Charlotte Whitt:	The Sprint Review demoes we did earlier, here it was demo by the developers. I have heard that these demos did take up too much of the developers time — and that was why these demoes were paused/stopped
00:47:22	Joe Reimers (EBSCO):	For us, "stakeholder" is too vague, too undefined, to be able to define.
00:48:25	Joe Reimers (EBSCO):	If we're defining "stakeholder" as "the community at large", then I vote "no" on sprint demos, and suggest we instead focus on periodic "feature highlights" videos.
00:49:07	Christine Schultz (EBSCO):	Reacted to "I don’t think enough..." with ➕
00:51:33	Amelia Sutton:	Reacted to "If we're defining "s..." with 👆
00:54:28	Charlotte Whitt:	POs out-side of EBSCO is definitely interested in knowing about new development
00:54:44	Charlotte Whitt:	But worried if these demos will cost too much developer time
00:55:21	Thomas Trutt:	back
00:58:17	Joe Reimers (EBSCO):	3 letters: U A T
00:58:39	Anne E. Ekblad:	I think the frequency and breadth of what's included is in question.
00:59:11	Christine Schultz (EBSCO):	Reacted to "I think the frequenc..." with 👍
01:00:04	Khalilah (EBSCO):	Innovation - where/how to communicate. Good point Owen.
01:01:28	Owen Stephens:	Agree @Joe Reimers (EBSCO)  that’s for new functionality to users - again not about the technical implementation not the user experience
01:02:12	Owen Stephens:	Everything we share publicly right now is focussed on the UX - and that’s mainly right. But I think we are missing a dev team to dev team sharing channel (outside relying on people sharing / asking on Slack)
01:02:33	Christine Schultz (EBSCO):	Reacted to "Everything we share ..." with 👍
01:02:58	Alvaro:	Reacted to "Everything we share ..." with 👍
01:03:02	Owen Stephens:	I want to say I appreciate you bringing this question Khalilah!
01:03:15	Christine Schultz (EBSCO):	Agreed, thank you Khalilah!
01:03:17	Owen Stephens:	I think this is important topics
01:03:18	Steph Buck (EBSCO):	Reacted to "I want to say I appr..." with 💯
01:04:27	Anne E. Ekblad:	Dashboard that includes: Sprint style demos; Demos from SIG meetings or other meetings; Current UATs.