2023-05-10 Product Council P&R Working Group Meeting Notes

Announcements

AirTable meeting

Wednesday 5/17 - 1:00-1:30 Eastern US, noon Central US, 7:00pm Germany

What questions do we have for AirTable?

• Provide a brief description of what we are aiming for, and then see what they think

• Will need to get a quote to better understand whether Airtable is feasible

• How many seats do we think we'll need?

• How easy is it to integrate with Jira?

• From previous meeting: Topics to discuss with Airtable:

  • Can they explain the Builder and Contributor roles further and explain what the different roles can do?

  • What role do people need to have to be able to vote? What is the best way to perform voting on issues using Airtable?

  • Are there webinars/pre-recorded tools available that we could review as we decide how to use Airtable?

  • How many seats do they think that we will need? If that turns out to be too expensive, are there ways we could gather votes and then have a member of PC/other input voting results

PO meeting

Today - 11:00am Eastern, 10:00 Central, 5:00pm Germany

• Jesse cannot make this.

Release vs. Fix Version: POs use both, it's a bit inconsistent.

Looking at two dashboards: By App and By Release. Khalilah preferred the "by release" version, we're not sure which is the best.

How would POs like to get priorities?

Who will be: Jen, Kristin

De-brief from Implementers meeting

Review notes: 2023-05-09 Product Council P&R Working Group Meeting with Implementers

How much maintenance would it take to keep these up? Right now, not sure how to move from release to release without it being manual.

• Maybe each SIG could redo their roadmap with new releases - would need a map between the apps and the SIG roadmaps

• Would probably need more training/use of Jira to make this possible - power users of Jira

• POs do indicate their features scoped for each release by the calendar, maybe we can tie this in.

• Could update three times a year: include Jira and free text versions of what will be worked on

• Release Planning Team (e.g., Poppy (R2 2023) - there is a deadline of May 29 for Quesnalia, that's when the roadmap could be updated

• Idea: each PC member could have a connection with making sure that various steps for Roadmap updating happen three times a year. E.g., liaison to SIG, PO (whatever development teams are working with the SIGs) to make the Roadmap stay current (could be a standing group to make sure work gets done)

  • This doesn't really address Prioritization

  • Bigger vision for the project is not reflected as much in this version

• We can even enhance and tie into the Release information, instead of maintaining the roadmap independently

• Addressing vision:

  • Maybe they need to reflected in Jira epics

Action Item: Jesse will draft up PC roles for managing the Roadmap