Report Date | Overall Status Update | Q4 Feature Count on Report Date |
|---|
|
| Functional | NFR |
|---|
| 2019-01-08 | Cate Boerema (Deactivated) - Critical path diagram for Q1 Circulation Features across Vega and Core teams can be found here: https://drive.google.com/drive/folders/1j4UuMl6bURkmslsKlVK_NlaY83H9Tr6-
- Issues:
- Does not account for work needed to factor time zone into due date/time calculations
- April 8 release date does not leave sufficient time to complete features. Can/should we push the release date from April 8 - April 19th?
- No bandwidth for 4 high priority Inventory features (UXPROD-1397, UXPROD-1396, UXPROD-1303, UXPROD-149) which are needed to support Batch Import features Chalmers needed for "go-live"
- Risks:
- Many interdependencies
- New teams and processes (esp Core: Functional)
- High-level estimates
- Core: Functional Team kickoff planning underway - Oleksiy, Jakub, Vicoria, Cate and Marc Johnson met today to work through slide deck. Goal is to follow agile best practices adopted elsewhere on FOLIO.
- Overall Q1 Planning:
Jakub Skoczen Last week of sprint 54 (last sprint of Q4) Functional work items update: - Already started working on some Q1 issues (usually UI-only, Michal, Aditya, Zak)
Q4 Release Management updates: OKAPI/RMB, Performance NFRs Performance: MODINVSTOR-215, latest status from Julian is that the issue and new mod-inventory-storage release will be ready by Wednesday Starting from this week and intensifying next week core back-enders will focus on various performance issues (Adam, Julian, Jeremy, William). Heikki is going to be away until the end of the year. Nassib will act as a partial replacement.
- Other:
- Working on the new Core Teams structure and meeting schedule for Q1, starting with core:functional and following with core:platform.
| | |
| 2018-12-11 | Jakub Skoczen Started sprint 53 Functional work items update: (Q4 work has been completed) Q4 Release Management updates: OKAPI/RMB, Performance NFRs
Jakub Skoczen Started sprint 53 Functional work items update: CIRC-154: check-in by barcode API (DONE, Marc) CIRC-146: Change status to "in transit" upon check-in (DONE, Marc) - Above means that all UXPROD-601 stories are now completed and wait for review (UICHKIN-17, UICHKIN-40, UICHKIN-41, UICHKIN-46, UICHKIN-60)
- UXPROD-118 work, considered at risk, will go ahead in Q4 (Dec/Jan) but likely we will decide against shipping it with Q4
CIRC-150: validation of check-in/check-out SP during loan CRUD (DONE , Kurt) required for UIU-485 (IN REVIEW, Aditya) CIRC-156: dereference patron group ID to display the name along with the request (DONE, Kurt) UIREQ-114 is now IN REVIEW
Q4 Release Management updates: - mod-feefines is required by FOLIO core modules (ui-users) but the release has not been made on time. CT made an out-of-band release. Trying to communicate with UNAM on the matter.
- External modules (Acq, ERM, MarcCat, etc) release deadline was last Friday (2018-12-07), most modules have been released on time but there are cases where some releases have not been made properly (Acq) or are still pending (mod/ui-marccat, ui-licences). CT is communicating with the POs and leads to try to help with those releases.
- This Friday (2018-12-14) is core UI modules release deadline. After all core UI modules are released, the DevOps team will attempt to build a fresh Q4 environment (most likely Monday 2018-12-17). The deadline for creating the environment is on Friday
- Q4 Release Management: all modules, interfaces (APIs) and their Q4 versions are tracked in this spreadsheet (updated at real-time):
https://docs.google.com/spreadsheets/d/1m966Ch822PUtsdvo01mS605ndB08ZhT7RRP3tnBRuX0/edit - Q4 Release is going according to plan:
https://docs.google.com/spreadsheets/d/1-4fMUyfnMhaMoJuEiwaABGu7ZzePvzhjya-nyV3dvvs/edit#gid=0
OKAPI/RMB, Performance NFRs Performance: MODINVSTOR-215: Julian implements solution agreed with EPAM DBAs throuh RMB-301 (IN PROGRESS), unfortunately no status since last week. - Starting from this week and intensifying next week core back-enders will focus on various performance issues (Adam, Julian, Jeremy, William). Heikki is going to be away until the end of the year. Nassib will act as a partial replacement.
Reference data loading functionality RMB-296 (DONE) and initial implementation in one of the modules (mod-inventory-storage) MODINVSTOR-216) is completed. We have decided against shipping the functionality in Q4 due to necessary deployment changes. It will be shipped with Q1 and all modules will be updated to implement this functionality.
Devops: Two new environments created: snapshot-core and snapshot-stable-core, with core modules only to allow for API updates - Working on non-standard deployment procedure to included edge-oai-pmh module in Q4, we will adress the tech debt around this in Q1.
FOLIO-1577: as mentioned above, an attempt to create Q4 environment will be made on Monday, Okapi can now generate a dependency graph to ease tracking dependency problems FOLIO-1548: STCLI-114 IN PROGRESS (ability to run modules locally and have them communicate with the black-box)
- Quality/Testing:
- Initial test coverage for nightmare (integration) UI tests has been completed for selected modules (ui-users) and shows coverage on the level of 30% percent. More work is needed to capture full coverage across core FOLIO modules. This work is grouped under FOLIO-1618, tasks will be handed out from next week.
| | |
2018-12-04 | | | |
| 2018-11-27 | Cate Boerema (Deactivated) - Several Core team Q4 features are at risk, but I am reluctant to move them out of the quarter, as we are hoping we can make at least some progress before feature freeze. POs for other teams are probably doing the same. Here's the full list of at-risk features across teams. There are 22 (of the total 107 targeted).
- I have tagged the features and stories coming out of the November Chalmers visit. View the list here.
- Circulation is still a risk area for Chalmers go-live. Specifically:
- Request policy still be designed (re-designed) and some elements may be moving to the Loan policy. Cate, Sean and Tania working to get this nailed down for the developers asap
- While some aspects of circulation are independent enough to be worked by a team other teams (e.g. loan and request policy CRUD, extending the loan rules editor) making these new policies effective will really need to be done by the Core team.
- Making policies effective needs to be done in exactly the same code being modified for other ongoing circulation features such as in transit to home location and fulfilling pickup requests. Not a lot of work can be done concurrently here.
- Title requests - still not clear what the plan is here.
- Library opening hours calendar - Sean is finding bugs and issues with this Qulto-developed app. Which team is responsible for maintaining it? Sean would be the best fit from a PO perspective given his other features are primary consumers of calendar data.
- Here is a list of circ related features likely needed by Chalmers to go live which will need to carry over in some form to Q1. The list is long and there are dependencies.
- Leipzig is hosting a self-built article index and are providing the data to a number of German libraries, most of them using vuFind discovery systems (are mostly hosted by Leipzig). The infrastructure/community is named finc. They are now getting ready to re-implement their configuration software on FOLIO. The code will of course be open source and re-usable, if there are any institutions interested in this kind of set-up. I have implemented a JIRA project (UIFC) for them to track their requirements.
Jakub Skoczen | | |
| 2018-11-20 | Cate Boerema (Deactivated) - Chalmers visit was very productive - Have a clearer understanding of their must-have workflows. Uncovered some gaps which will be logged as features in JIRA and discussed with the relevant SIGs
- Need to decide on sprint review schedule during the holiday, as the normal cadence would have the next demo on Christmas day. Some options:
- Tuesday Dec, 18
- Thursday January 3
- Tuesday January 8 (one week before release - too late?)
- NOTE: Release is Monday January 14
- Risks:
- Circulation is a very high risk area for Chalmers' ability to go live
- Cap plan model has been updated
- Need to review feasibility of Q1 targets with POs and get back to Product Council and Chalmers with our findings
Jakub Skoczen | | |
| 2018-11-13 | | | |
| 2018-11-06 | Cate Boerema (Deactivated) - PO deadline for first pass at Q1 targets is end of week. Features that are clearly not going to make Q4 may be moved to Q1 as part of this effort. POs will update on this report if there is feature slippage.
- POs will also be tagging Q4 features that are at risk for deferment or splitting by end of week so we can get a better sense for how we are tracking. I'll link some reports to this page once the tagging is complete. Many features appear to be slipping. Some at-risk themes from Circulation: request fulfillment, In transit to home location, patron notices, title level requests etc.
- Updated the Chalmers table below based on the latest rankings - a couple of new epics appear in the table, as they contain 1 or more feature now needed for go-live
- Theodor will work with Chalmers to revisit their go-live features again to make sure they are accurate and (potentially) reduce scope
Cate, Ann-Marie, Khalilah and Theodor will be at Chalmers next week. Top priority: review existing functionality in detail (demos), identify gaps, determine if gaps are represented in the UXPROD backlog and prioritized appropriately. This will ensure we are clear on priorities. Spoke with Victoria Rabykina (new scrum master) who highlighted some issues with our JIRA maintenance (stories without features, features without stories, too many features). I talked her through the UXPROD "rules" and she'll be following up with her POs to get things cleaned up. She may also have some good ideas for new reports and processes .
Jakub Skoczen Jakub Skoczen | | |
| 2018-10-30 | Cate Boerema (Deactivated) - Deadline for early adopter rankings is end of week (November 2nd)
- Once rankings are complete, gap analysis team will need to discuss how best to approach Q1 planning
- E-Resource Usage data and related reporting features and Q4 targets have been revised by the Leipzig team - will want to update the Cap plan to incorporate these (can wait until after the early adopter rankings have been completed)
- Risks:
| | |
| 2018-10-23 | Cate Boerema (Deactivated) Release Planning:
Discussed Loan Policies integration with the Opening Hours module with Sean (PO, EBSCO) and Istvan (Qulto). We discussed two options to proceed: Extending Opening Hours module with endpoints to calculate loan periods Performing calculation within mod-circulation using existing endpoints from the Opening Hours module Both are viable solution and would be developed by the Vega team
Discussed next steps for FOLIO CI environments with the following conclusions: Short-term: introduce PR build and “previews” to catch issues early before they reach master branches of individual projects, to catch dependency issues at PR time, allow POs to review features before they are merged to master branches Long-term: we have identified a need for a truly clustered, multi-tenant CI/CD environment to address both the functional (e.g ability to run multiple versions of the same module to support different UI configurations and allow developers to “hot plug” modules) and non-functional (scalability problems that the current environments face). We have discussed that the current devops resource gap will not allow us to make substantial progress on building the env in Q4 so we will begin with a technical design for such environment.
More information: https://folio-org.atlassian.net/browse/FOLIO-1550?focusedCommentId=38292&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-38292
| | |
| 2018-10-23 | Cate Boerema (Deactivated) Release Planning:
Discussed Loan Policies integration with the Opening Hours module with Sean (PO, EBSCO) and Istvan (Qulto). We discussed two options to proceed: Extending Opening Hours module with endpoints to calculate loan periods Performing calculation within mod-circulation using existing endpoints from the Opening Hours module Both are viable solution and would be developed by the Vega team
Discussed next steps for FOLIO CI environments with the following conclusions: Short-term: introduce PR build and “previews” to catch issues early before they reach master branches of individual projects, to catch dependency issues at PR time, allow POs to review features before they are merged to master branches Long-term: we have identified a need for a truly clustered, multi-tenant CI/CD environment to address both the functional (e.g ability to run multiple versions of the same module to support different UI configurations and allow developers to “hot plug” modules) and non-functional (scalability problems that the current environments face). We have discussed that the current devops resource gap will not allow us to make substantial progress on building the env in Q4 so we will begin with a technical design for such environment.
More information: https://folio-org.atlassian.net/browse/FOLIO-1550?focusedCommentId=38292&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-38292
| | |
| 2018-10-16 | | | |
| 2018-10-09 | | | |