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 78
Next »
Suggest ideas for FOLIO reports and dashboards here
Weekly Updates
Report Date | Overall Status Update | Q4 Feature Count on Report Date |
|---|
|
| Functional | NFR |
|---|
| 2018-12-04 | Cate Boerema (Deactivated) - Index Data having company meetup so I am running the Core team roundups
- Gap analysis team is working very hard to get the Q1 planning in place. This means:
- UXPROD feature refactoring
- Feature distribution across teams
- Feature estimating
- Risk: there is a LOT of concurrent circulation work that needs to happen. We need to be very careful about how this is distributed across teams.
- Goal is to have the cap plan updated tomorrow
| | |
| 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 | | |
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 |
|---|
| 12-07-18 | | UXPROD-1119 will not be totally implemented–manual patron blocks will be able to be created UIU-674 but not enforced UIU-675. Enforcement UIU-675 is less than a week behind the freeze date of December 7 for Q4 2018. This is go-live feature for Chalmers. Perhaps Chalmers doesn't need to wait until the Q1 2019 release in April if UIU-675 is ready this week? Cate has recommended that Holly check with Jakub. |
| 12-06-18 | | UXPROD-656 (CRUD for batch import rules) was (in retrospect) a huge feature. It was renamed as Data Import Infrastructure and Planning and remains in Q4 2018. Other features broken out from it: UXPROD-1376: file extension settings (Q1 2019) UXPROD-1377: CRUD for Job profiles (Q1 2019) UXPROD-1378: CRUD for Mapping profiles (Q1 2019) UXPROD-1379: CRUD for Action profiles (Q1 2019) UXPROD-1380: CRUD for MARC mapping profiles (Q1 2019) UXPROD-1381: CRUD for EDIFACT mapping profiles (Q2 2019) UXPROD-1382: CRUD for Delimited mapping profiles (Q2 2019) |
| 12-06-18 | | UXPROD-1038 (ISBN Normalization): split into 2 features. This one will remain in Q4 2018 and cover preparation and design. UXPROD-1394 marked for Q1 2019 and will cover implementation |
| 12-05-18 | | UXPROD-1217 As of today, functionality to extend the existing loan rules editor to accommodate additional policy types (e.g., request policies, notice policies) has been moved to Q1-2019. |
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
|