FOLIO Q4 2018 (Aster) Weekly Status Report

Owned by Cate Boerema (Deactivated)
Last updated: Jan 24, 2019
3 min read


Suggest ideas for FOLIO reports and dashboards here


See the Q4 2018 Release Dashboard and the Chalmers Release Dashboard in JIRA for more charts and click-through to feature details.

See /wiki/spaces/DQA/pages/2654395 for bi-weekly updates on software quality.

Q4 2018 Release Milestones


Weekly Updates

Report Date

Overall Status Update



2019-01-14

Cate Boerema (Deactivated)

  • Q4 RELEASED

  • User-facing release notes available here: Q4 2018 (Aster) Release Notes

  • Features closed/completed in Q4 2018: Getting issues...

    • Getting issues... functional
    • Getting issues... NFR

Click to view status update history

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

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


DateProduct OwnerNotable Risks, Issues and/or Changes
2019-01-11

Cate Boerema (Deactivated)

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-14Darcy BranchiniI 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

sthomas (Deactivated)

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

Dennis Bridges

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  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
Refresh

Chalmers for Go-Live Feature With No PO

key summary fixversions epic link
Refresh

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


MetricDescription
Closed release features

Features released on January 14, 2018

Getting issues... Total

  • Getting issues... Functional
  • Getting issues... NFR
Targeted 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
Split release featuresNumber of Q4 features that were not fully completed and needed to be "split" (carry-over features were created for unfinished work)

Getting issues...

Percent ClosedClosed features/Target features

70%

(up from 30% last quarter)