55 min | PO meeting wrap up and action items | All
| We sum up our meeting with the POs: 2024-06-26 Product Owner Meeting We came away with several action items: Prioritize the list of cross app tickets (see https://folio-org.atlassian.net/jira/dashboards/10270) There are currently 24 issues on the list, including some closed issues that represent discussions that did not graduate to development tickets and need to be resolved. We are going to first prioritize these on a spreadsheet rather than make changes in Jira: | Lref gdrive file |
|---|
| url | https://docs.google.com/spreadsheets/d/1nFhq4OeAsOgABos_1OQ7zGBz0lCgyeSrn1u3z0yGqIM/edit?gid=0#gid=0 |
|---|
|
Once we have prioritized those issues, invite the POs to our meeting or return to theirs. The POs are setting up a regular review. Designate a liaison/champion who can help highlight App Interaction issues and serve as a resource to the POs. Our first exploration should be to figure out what the boundaries of this role would be. TARA will be our designated PO liaison as we explore the role, and will attend upcoming PO meetings. Once we have a sense of the role/needs, we can decide who makes the most sense. (We want to try this for a few months.)
We note that this puts a lot of work on the App Interaction SIG. It would be ideal to have the relevant POs attend our meeting when topics are discussed. We feel like announcing the meeting topics in advance hasn’t worked well for getting POs through the door. We think that shifting our focus to being a resource will be a good thing to try. Charlotte suggests that we should choose a target area to focus on.
Martina notes that it’s fine if development is not immediate--that is not the goal. Awareness, alignment, and collaboration are the goal. Should we focus on Stripes topics? Do we have the ability to identify them?
|