Report Date | Overall Status Update | Q1 Feature Count on Report Date |
|---|
|
| Functional | NFR |
|---|
| 2019-04-02 | Cate Boerema (Deactivated) - Met with Chalmers to review Requests functionality and there are no major holes for go-live aside from title level requests
- Still finalizing Q2 scope by team - should be completed and updated in JIRA by end of week: https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=10604
- POs still working to pull together stories for Q2
- Lots of bug fixing and triaging happening
- So far only one release blocker bug has been identified related to Calendar:
MODCAL-38
-
Getting issue details...
STATUS
Jakub Skoczen Mid Sprint 60 Q1 Release updates: - Bellis (Q1) environment is up and running: http://folio-bellis.aws.indexdata.com/
All "platform-complete" modules have been released. Pending possible bugfix releases for mod-finance-storage (MODFISTO-5), mod-erm-usage (MODEUS-12) and mod-users (performance issues) issues around "building" a bundle (STCOR-360) Work on integrating "edge" modules into Q1 is ongoing, ETA: end of sprint Work on updating FOLIO install documentation (single-server "folio-install", Ansible independent) and Vagrant images for Q1
- Performance
| | |
| 2019-03-26 | Cate Boerema (Deactivated) - EBSCO early implementers meeting this week
- Q2 planning happening this week
- Features should have been created and estimated
- Mark V will be running them through the cap plan
- Will need to re-prioritize with POs where capacity is insufficient
- Core functional sprint 60 kicked off this week
- Anatoli going to another team mid sprint
- Last sprint for Aditya (moving to ERM)
- Jeremy Huff rotated on from TAMU
- Big focus on bug fixing (many seem to be ui-only)
- Also doing feature work that was prioritized by Chalmers (e.g. Check in notes and Inventory delete)
Jakub Skoczen
Completed Sprint59, started Sprint 60 Q1 Release updates:
All "platform-core" modules have been released. On the 25th (midnight) ALL remaining modules were due. The Core Platform will confirm that releases have been made and notify about missing releases or dependency issues today (‘q1-2019-release’ channel) The Q1 ‘platform-core’ environment is automated through the PRs from “q1-2019-rc” branch: Similar automation is planned for Q1 ‘platform-complete’ environment. All known issues regarding module integration for Q1 have been resolved or are being addressed in this sprint (e.g 4 edge module integration issues remain)
Performance fixes (Q1) – in Sprint 60 addressing Users performance issues reported during the BugFest, issues in JIRA categorized with "labels = q1-performance"
| | |
2019-03-19 | Cate Boerema (Deactivated) - PO plan presentations are still underway and, once those have been completed, we'll need to run desired features through the cap plan (next week)
- In the meantime, here is the current high-level thinking on the work to be split across Core Functional and Vega in Q2
Vega Policy override carry over Send patron notices (email only) Due date time zone cleanup, if needed Closed library due date management carry over, if any Bug fixing Maybe:
Core Functional - Magda, Martin Tran and Matt Reno (the 3Ms) are creating focused, Core Functional subgroup to work on SIP2 and Title Level Requests (both important features needed by Chalmers to go live)
- This will reduce the backend capacity on the main Core Functional team to just 1.5 FTEs
- This seems okay in that most work queued up in front-end heavy and many bugs seem to be in the UI, as well
Jakub Skoczen - Updates from the Core: Platform team
- The team is in the middle of Sprint59
- Q1 Release updates:
- All "platform-core" modules (Core: Platform, Core: Functional, StripesForce, Vega, UNAM) have been released
- The (initial and temporary) Q1 environment for "platform-core" has been set up:
- http://platform-core-250-3.aws.indexdata.com
- the process used this time around relies on the work delivered by CP in Q1, namely (Epics):
- FOLIO-1519 Automatic loading of sample and reference data
- FOLIO-1577 Automated builds for FOLIO 'release'
- it includes all performance fixes provided in Q1:
| type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
- Next important date for Q1: 25th of March, a deadline for all remaining modules from 'platform-complete' (all other teams)
- FOLIO-1630 include "edge" modules in daily snapshot/testing builds – work resumed this Sprint on unblocked modules (some module remain blocked on updates to edge-common 2.0)
- Core Platform is working on install notes and scripts for Q1 (independent from Ansible playbook)
- Core Platform is working on remaining request to include external modules into snapshot/testing (and likely Q1) that came late this quarter, some of them are blocked by work by external teams (team leads notified)
| | |
| 2019-03-12 | Cate Boerema (Deactivated)
Jakub Skoczen - Updates from the Core: platform team:
- The team has started Sprint59 on Monday
- Performance work:
- Release Management and CI/CD
- data loading work (prerequisite for automated "release" builds) is planned for completion within the next couple of days. Once completed Ansible data-loading roles will be disabled for folio-snapshot and folio-testing.
- Prioritized various task for adding modules to folio-snapshot/testing: staff slips, erm-usage, invoicing modules, mod-source-record-storage agreements (blocked in OKAPI-710)
- Included in the sprint unblocked tasks for adding edge-rtac (edge-oaipmg was still blocked at the begining of the sprint)
| | |
| 2019-03-05 | | | |
| 2019-02-26 | | | |
| 2019-02-12 | Cate Boerema (Deactivated) Circulation critical path review - Core Functional is still behind on extending loan rules (originally targeted to be done by mid sprint 56). Now work may continue beyond sprint 58.
- Vega was also delayed with patron notices and, therefore, have not been blocked by this.
- Due to delays in extending loan rules and the need for more tech design, we are no longer tracking to deliver the functionality needed to make patron notices effective in Q1
- Request policy basic CRUD is complete, but the work to make the policies effective will be delayed due to delays in extending loan rules
- Backend timezone compliance (not part of the original Q1 scope) has been prioritized for Vega, as, without it, due dates and times will not be accurate.
Core Functional is also behind on hold shelf expiry period work, but, again, Vega is not ready to start on the next step (request expiration) - Vega has uncovered some new work in calendar and closed library due date management that needs to be prioritized (stories still TBD)In summary:
- Delays on Core: Functional
- Delays on Vega
- Large new feature (plus other smaller issues) prioritized for VegaFeatures at risk and/or certain not to make Q1 release:
- Good news: additional backend developer (Anatolii from EPAM) joining Core Functional team (ramping up this week and full-time as of next)
Ann-Marie working on tagging projects in SonarCloud to make it easier for POs, scrummasters and tech leads to review test coverage by development team and/or app | | |
| 2019-02-05 | Cate Boerema (Deactivated) - Circulation critical path review
- Core Functional is still behind on extending loan rules (originally targeted to be done by the beginning of this week) but Vega isn't ready for this work anyway
- Vega is still working on technical designs for patron notices and, therefore, will not be able to make use of the extended loan rules editor until sprint 57 at the earliest
- Due to delays in extending loan rules and the need for more tech design, we are no longer tracking to deliver the functionality needed to make patron notices effective in Q1
- Request policy basic CRUD is complete, but the work to make the policies effective will be delayed due to delays in extending loan rules (still tracking for Q1)
- Backend timezone compliance (not part of the original Q1 scope) has been prioritized for Vega, as, without it, due dates and times will not be accurate.
- Core Functional is also behind on hold shelf expiry period work, but, again, Vega is not ready to start on the next step (request expiration). CF is still working hard to wrap up their portion and it looks like the delay may be limited to one week.
- Vega has uncovered some new work in calendar and closed library due date management that needs to be prioritized (stories still TBD)
- In summary:
- Delays on Core: Functional
- Delays on Vega
- Large new feature (plus other smaller issues) prioritized for Vega
- Features at risk and/or certain not to make Q1 release:
- Good news: additional backend developer (Anatolii from EPAM) joining Core Functional team (ramping up this week and full-time as of next)
- Ann-Marie working on tagging projects in SonarCloud to make it easier for POs, scrummasters and tech leads to review test coverage by development team and/or app
| | |
| 2019-01-29 | | | |
| 2019-01-22 | Cate Boerema (Deactivated) - Q4 UXPROD is all tidied up! POs have closed all features, splitting as needed. See dashboard
- Q4 2018 (Aster) Release Notes are up
- General Cross Release Statistics page has been created with a few cross-release metrics
- The number of features closed in Q4 more than doubled relative to Q2 and Q3
- Percent of targeted features that were closed more than doubled as well (we are getting better at planning)
- Caveat: This is not an exact science. Features are of variable sizes and closed does not equal complete. Many features that are closed are not fully complete (at the end of the quarter we "split" incomplete features and create carry-over features for remaining work. We had 18 of these splits in Q4 (no data from previous quarters).
- Still, this is good progress and we are headed in the right direction
- Core Functional team is getting the hang of the new Agile ceremonies
- Chalmers
- Most of Chalmers Q1 stories are in Resource Access
- Risks
- Many dependencies between teams (Vega and Core)
- New teams and processes
- Lots of bugs to fix and tests to catch up on
- Issues
- Marc Johnson down to 25 hours per week which means something needs to be dropped from Core Functional in Q1. Looking into what options we can give to Chalmers on this.
- No support for timezone on the back-end which will make the due date calculation work being done by Vega inaccurate. No bandwidth for this work in Q1.
- Falling behind schedule per critical path diagram
Jakub Skoczen
Mid sprint 55, first sprint of Q1 Core: Functional work items update: see Cate's update - provided initial DoD for the team — to be discussed and agreed this week
Q4 Release Management updates: completed
Core: Platform update:
| | |
| 2019-01-15 | Jakub Skoczen Started sprint 55, first sprint of Q1 Core: Functional work items update: Q4 Release Management updates: Core: Platform update: - Kick-off meeting with Aleksandr went well. Established the Scrum board and filter to capture the Platform/DevOps issues.
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). Heikki is going to be away until the end of the year. Nassib will act as a partial replacement.
Cate Boerema (Deactivated) - Working with POs to get UXPROD cleaned up so we can get final stats and release notes for Q4 2018 release. By this point, all Q4 2018 features should be closed and they are not.
| | |
| | | |