Page Comparison

Ranking the JIRA tickets to come up with the Q3 development priorities

Planning steps - have reduced developer capacity by 50%

• 40% allocated for bug fixing
• 10% for performance tests & improvements

Teams have already been assigned and show up in JIRA -

Core Platform doesn't get assigned like the others, have to also respond to urgent problems from all apps

Detailed plans: Capacity Planning spreadsheet - features prioritized by community gets a rank (from library rankings) - POs also rank based on their knowledge of dependencies & other factors - Green - Q3, Yellow - Q4 tasks.  This spreadsheet can show up dependencies and things like mismatches between FrontEnd/BackEnd needs

https://docs.google.com/spreadsheets/d/12wNBLIMoexSN-upjRLa7SXYCiKTiN80GLB4sf9ooYjc/edit - Spreadsheet link

Question about how features get changed - UXPROD ?? was an example - in that case just ran out of developer resources, will try to work back in for Q4 - Harry encouraged people to talk to the PO when these come up

KKH - could we get updates (PC & Implementers) about major developments, features that get dropped or delayed - maybe someone in the community could help out

AMB - maybe an at-risk dashboard?  This could be feasible, also people could set themselves as a watcher for particular features to keep updated - better comments will be helpful, too - also labels for major changes

Tod - is there a high level way of looking at major changes? 

2020 Planned Features: https://issuesfolio-org.folioatlassian.orgnet/secure/Dashboard.jspa?selectPageId=11003

Q3 2020 (Honeysuckle) Dashboard: https://issuesfolio-org.folioatlassian.orgnet/secure/Dashboard.jspa?selectPageId=11202

PO MVP and Rounds Feature Status: https://docs.google.com/spreadsheets/d/1VgyCrNBNAXIGL12ynMNd35o1CyE9ONP1aj4HitqsZb8/edit

See July 16 PC notes and recording - Anton gave full update there

From PC notes:

• Bugfest June 22-26: 91% passed, ~150 more test cases than last time, nearly double the number of testers so FOLIO staff were able to take fewer cases.  Texas A&M and Chicago added testers for the first time.  Very few retests this time.
• Only 37 unresolved cases
• Emphasis on schema update testing and found some issues that Texas A&M addressed and developers did some pre-testing and identified more issues
• Have 29 issues for the hot fix

Deferred to next week