Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 91
Next »
Suggest ideas for FOLIO reports and dashboards here
Weekly Updates
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.
| | |
Q4 2018 Release Features (Functional) by Status
Getting issues...
The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.
Q4 2018 Release Features (NFR) by Status
Getting issues...
The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.
Status | |
|---|
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 |
|---|
| 2019-01-11 | | I split UXPROD-1238, formerly known as "Location and Service Point CRUD Enhancements Q4 2018": - The carry over work is now contained in UXPROD-1416 (Location and Service Point CRUD Enhancements Continued)
- To better describe what was actually completed in Q4, I renamed UXPROD-1238 "Enable Filtering of Location Records by Institution, Campus and Library"
- While only one of the 4 stories was completed, it was bonus work - this feature was not planned for Q4 (we were able to make some progress on while UI developers were waiting for backend dependencies to complete)
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). |
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
Getting issues...
(UXPROD features) that have not yet been ranked by Chalmers. As these features are ranked, we should expect the features needed below to increase.
Remaining Features Needed by Chalmers to Go-Live
Unable to render Jira chart macro due to an execution error. Chalmers Go-Live Features at Risk in Q4
These may be carried over into Q1 2019 (either entirely or in part)
| key |
summary |
assignee |
status |
epic link |
labels |
development team |
Chalmers for Go-Live Feature With No PO
| key |
summary |
fixversions |
epic link |
Features Needed by Chalmers for Go-Live
The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.
Q4 2018 Release History
| Metric | Description |
|
|---|
| Current features | Features targeted for Q4 release as of today |
Getting issues...
Total -
Getting issues...
Functional
-
Getting issues...
NFR
|
| Baseline release features | Features targeted for Q4 release on October 9, 2018. Notes: - The baseline features were not finalized until about a week after the start of the development period, as the Acquisitions issues needed to be distributed across development teams
- Included features will need to be further adjusted due to resourcing changes, but this can be considered the baseline
|
Getting issues...
Total -
Getting issues...
Functional
-
Getting issues...
NFR
|