Suggest ideas for FOLIO reports and dashboards here
Page Properties | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
Dynamic release data with weekly status updates | |||||||||||
Q4 2018 Features in JIRA (updates dynamically) | |||||||||||
Functional Features Today |
| ||||||||||
NFRs (Non-Functional Requirements) Today |
|
Weekly Updates
Functional
NFR
Report Date | Overall Status Update |
---|
Q4 Feature Count on Report Date
2019-01-14 |
|
|
|
|
|
|
|
- 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
- In transit to home location (not to fulfill request) - This feature required lots of new plumbing and is at risk of not being completed in Q4. It is a pre-requisite for Fulfill pickup requests (see next bullet)
- Fulfill pickup requests - This can't begin until In transit to home location (previous bullet) is complete. It is a very large feature and likely to not even be started in Q4.
- Extending Loan Rules Editor to target additional policy types - Critical to the completion of Requests (request policies) and Patron notices (notice policies). Will likely need to be pushed to Q1.
- Setup/configure patron notice logic (Patron Notices Policies) - Critical to the completion of patron notices. Likely to be pushed out of Q1.
- Scheduler - Prerequisite for completion of patron notices and not started (wasn't actually targeted for Q4, but should have been)
- 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
|
CIRC-154: check-in by barcode API (IN PROGRESS by William, to be handed off to Marc). William will issue a PR today and Marc will handle the review and any remaining work, once completed it will allow to unblock CIRC-146
CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS handed over from Jeremy to Marc). Emma, Marc and I had a good meeting about specific uses cases and requirements not flashed out earlier (e.g repeated check-in/scan). We have also discussed extensions to handle pickup requests (a backend prerequisite for UXPROD-118), they seem quite manageable and contained but we decided that they will not be in scope for CIRC-146 to avoid putting UPROD-601 under threat.
CIRC-150: validation of check-in/check-out SP during loan CRUD (IN PROGRESS re-assigned to Kurt from Jeremy) required to complete UIU-485
CIRC-151: Make mod-circulation Service Point enabled (DONE, Kurt)
CIRC-156: dereference patron group ID to display the name along with the request (IN CODE REVIEW, Kurt) no longer blocks UIREQ-114, needs handling of permissions
Cross team
Kick-off meeting about the PubSub support in FOLIO based on the earlier proposal from Adam and Jakub happened last Wednesday, it has been decided that the proposal meets EPAMs requirement and the EPAM team will move ahead with implementation of mod-pubsub and "scope" functionality in Okapi.https://docs.google.com/document/d/1L0qJ6VEmlKU4UCfznnc7du9qPZpjVq3DhcW68leIgEY/edit
OKAPI/RMB, performance NFRs
MODINVSTOR-215: During the meeting with EPAM Postgres experts on Tuesday it has been decided that Julian will continue with a solution similar to what has been proposed and he will implement the solution in RMB. The Core Team will not need more support from EPAM. (see RMB-301)
Devops:
FOLIO-1577: Created automated builds for 'next-release' (IN PROGRESS, John) – there were missing releases blocking completion of this issue and it has become the focus of the last devops call. We have decided that it is not devops responsibility to request specific backend or front-end module releases, on the contrary – new "next-release" builds should be triggered by availability of new module releases. The specific dependency issues that prevent the current build are being investigated by Marc and John. We have decided to put additional guards in place to ensure that future releases are free from those dependency issues (OKAPIFOLIO-1548: Create a lighter-weight folio/testing-backend VM – the SPIKE has concluded and the approach is to slim down the Vagrant VM and provide ability to load additional modules dynamicall (STCLI-15, STCLI-114)
|
|
|
|
|
|
Click to view status update history
Q4 2018 Release Features (Functional) by Status
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Charts | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Q4 2018 Release Features (NFR) by Status
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Jira Charts | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Status | Definition |
---|---|
Open | Feature is waiting to be picked up by PO. |
Draft | Feature is being worked on by the PO. Discussions are happening with the SIGs and sub-groups, mock-ups are being created. Analysis is underway. |
Analysis Complete | PO analysis is complete. Stories are written and mockups have been created. |
In Progress | Analysis is complete and development is underway. While it is often the case that we begin development on some aspects of a feature before the PO’s analysis work has been completed, please do not move a feature into Development (In Progress) until after Analysis is Complete. This is important so we can maintain visibility into what features that have remaining PO work. |
In Review | Most or all stories in the feature are In Review (being tested). |
Closed | All stories in the feature have passed test and are closed. Feature is complete. |
Product Owner Updates
Date | Product Owner | Notable Risks, Issues and/or Changes | ||
---|---|---|---|---|
20182019-01-11-09 | Moved all issues relating to Invoicing to Q12019 as they are not priority for the upcoming go-live. Focus will shift to Receiving.
Moved issues relating to Finance
At Risk/Will Split
Adding to Q4 but at risk depending on capacity UXPROD-187, UXPROD-186 Recent meetings with early adopters have Identified these as a higher priority than the finance application | I split UXPROD-1238, formerly known as "Location and Service Point CRUD Enhancements Q4 2018":
I split UXPROD-1138 (Requests Pick List: CSV Export) because the csv export is missing a single column (inventory dependencies were not in place). Carry over work is not contained in Add Copy Number to Requests CSV (UXPROD-1417) | ||
2019-01-14 | Darcy Branchini | I split UXPROD-675 (CRUD patron notice templates). The carry over work is now contained in UXPROD-1421 (Pre-defined patron notices). There are also a few bugs that reported from the original CRUD patron notice templates. Those are captured as UICIRC-160, UICIRC-159, UICIRC-143, and UICIRC-161. | ||
2019-01-17 | I split UXPROD-744 (Loan Policy: Impact on loans part 2 - Q4-2018 Release). The carry over work is now contained in UXPROD-1440 (Loan Policy: Impact on loans part 3 - post-Q4-2018). | |||
2019-01-18 | UXPROD-678 was split for the Q4 release. Some of the field mapping work needs to be updated as updates have been made to the orders schema. The work that has carried over is now covered by UXPROD-1444. |
Click to view product owner update history
Chalmers
The focus of Q3 and Q4 2018 is delivering the features required by Chalmers to go live. For this reason, we will take a closer look at those features in this portion of the report. See the Chalmers Release Dashboard in JIRA for these and more click-through reports.
NOTE: There are also
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Remaining Features Needed by Chalmers to Go-Live
Jira Charts | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Chalmers Go-Live Features at Risk in Q4
These may be carried over into Q1 2019 (either entirely or in part)
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Chalmers for Go-Live Feature With No PO
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Features Needed by Chalmers for Go-Live
Jira Charts | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Q4 2018 Release History
Metric | Description |
---|
Closed release features | Features |
released on January 14, 2018 |
|
|
|
|
|
|
|
Targeted release features | Features targeted for Q4 release on October 9, 2018. Notes:
|
|
|
|
| ||||||||||||
Split release features | Number of Q4 features that were not fully completed and needed to be "split" (carry-over features were created for unfinished work) |
| ||||||||||
Percent Closed | Closed features/Target features | 70% (up from 30% last quarter) |