Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/867230970
Dial (for higher quality, dial a number based on your current location)
US Toll: +1 408 638 0968 or +1 646 558 8656
Meeting ID: 867 230 970
International numbers available: https://zoom.us/zoomconference?m=HFOYojqG6P0eOobNily-kmpgCrJ9eJQ_
Aaron Trehub, Alexis Manheim, Anya Arnold, Charlotte Whitt, Gang Zhou, Gar Sydnor, Harry Kaplanian, Jesse Koennecke, John Ballestro, Karen Newbery, Khalilah Gambrell, Kirstin Kemner-Heek, Karen Newbery, Kristin Martin, Martina Schildt, Martina Tumulla, Maura Byrne, Mike Gorrell, Owen Stephens, Peter Murray, Sharon Wiles-Young, Stephanie Buck, Tiewei Liu, Zak_Burke
Community Council - Kirstin
New FOLIO members – waiting for MoU’s:
|15 min||Capacity Planning Team Roles||Jesse|
FOLIO Capacity Planning originally came about in 2019 when the focus was on the FOLIO MVP to coordinate the developer resources to make that happen. The FOLIO Capacity Planning Team charge drafted a new charge a few months ago:
The Capacity planning team exists mainly as a service to POs and the overall FOLIO project to provide and recommend in the following areas:
The FOLIO release process
Define and plan releases and deadlines for both full named releases and hot fixes
Provide recommendations for “Go” and “No-Go” decisions
Support PO's in helping decide if a defect has reached a level of severity to make it into a hotfix
Identify problem areas that must be addressed relating to a release or the overall release process while also suggesting solutions
Support PO's having capacity issues and helping suggest improvements
Help drive the community feature ranking process and suggest improvements to make that process more useful to FOLIO Product Owners
Help place new developers contributed to FOLIO on teams that can make use of their skillsets
Much of the work of capacity planning has moved to the Technical Council (criteria for adding apps, for instance). Capacity planning works with product owners and the release team to determine when a release is ready and whether hotfixes are needed. They also help with moving developers and code responsibility around as people come in and leave teams and help assign new developers to existing teams. Historically, capacity planning also helped drive the process of ranking features. There are not many community developers left on the project, so that role has decreased significantly.
Recognizing the changing needs, this spreadsheet shows a possible distribution of roles and responsibilities (Cap Planning team centric) with the capacity planning group turning into a release planning group.
When thinking about release planning, the existing capacity planning group looks at the functionality that product owners are planning for each release and shape the general size and scope of releases.
Capacity Planning has not had an elected member of the Product Council on it, and that seems odd. In reformulating this into the release planning team, it would be good to address this. (Two people that are on the capacity planning group now are also elected members of Technical Council.) Sharon Wiles-Young, Martina Schildt, and Jesse Koennecke volunteered to sit in on the finalization of the group charter. The group meets at 9am Eastern U.S. time every other Monday.
|5 min||Future meeting topics:||Jesse||Prioritization Process WG update (Tentative: March 31)|
Zoom chat log
00:08:58 Kristin Martin: Just put it in chat. 00:11:06 Kirstin Kemner-Heek: I meant: registration will hopefully soon be open to WOLFCon - I'm sorry! 00:13:28 Kirstin Kemner-Heek: https://openlibraryfoundation.org/about/wolfcon/upcoming/ 00:24:11 Harry: The FOLIO Capacity Planning Team charge The Capacity planning team exists mainly as a service to POs and the overall FOLIO project to provide and recommend in the following areas: ï‚§ The FOLIO release process ï‚§ Define and plan releases and deadlines for both full named releases and hot fixes ï‚§ Provide recommendations for â€œGoâ€ and â€œNo-Goâ€ decisions ï‚§ Support PO's in helping decide if a defect has reached a level of severity to make it into a hotfix ï‚§ Identify problem areas that must be addressed relating to a release or the overall release process while also suggesting solutions ï‚§ Support PO's having capacity issues and helping suggest improvements ï‚§ Help drive the community feature ranking process and suggest improvements to make that process more useful to FOLIO Product Owners ï‚§ Help place new developers contributed to FOLIO on teams that can make use of their skillsets 00:24:32 Kristin Martin: I hate to miss this discussion, but I will need to go 00:29:03 Mike Gorrell: https://docs.google.com/spreadsheets/d/1vvDiqP4wZOQN6L7ULgbJ9y_-JEhYeXIGjmmTFx1Yd_Q/edit#gid=0 00:31:43 Zak Burke: I need to drop for another meeting. 00:40:45 Owen Stephens: I think thatâ€™s the crux of the question - what makes those things â€œimportantâ€ - whatâ€™s the criteria? 00:41:09 Owen Stephens: An alternative way of planning releases would be to have absolute deadlines and just release whatâ€™s available at that point 00:43:14 Harry: Owen, in general, that is exactly what we try to do. However, sometimes due to dependencies, it can get more complicated. 00:52:57 Peter Murray: The new Alabama team ("Bama") working on the Calendar app is a good example of what Harry was describing. 00:58:53 Mike Gorrell: Currently we meet at 9am on Mondays 00:59:05 Mike Gorrell: Yes - every other week 01:14:28 Khalilah Gambrell: Thanks Jesse.