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- |
- Working on the new Core Teams structure and meeting schedule for Q1, starting with core:functional and following with core:platform.
14 |
- 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
- Issues:
- 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:
- Q1 Release Dashboard is up: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10514
- Chalmers go-live dashboard is still the same link: https://issues.folio.org/secure/Dashboard.jspa?selectPageId=10505
- There are 25 go-live features that are not in for Q1 - would be worth taking a look through
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:
https://docs.google.com/spreadsheets/d/1m966Ch822PUtsdvo01mS605ndB08ZhT7RRP3tnBRuX0/edit
https://docs.google.com/spreadsheets/d/1-4fMUyfnMhaMoJuEiwaABGu7ZzePvzhjya-nyV3dvvs/edit#gid=0
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
|
|
|
|
|
|
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 |
---|---|---|
2019-01-11 | 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) |