Suggest ideas for FOLIO reports and dashboards here
Overall Status Update
Q1 Feature Count on Report Date
Circulation critical path review
Ann-Marie working on tagging projects in SonarCloud to make it easier for POs, scrummasters and tech leads to review test coverage by development team and/or app
Q1 2019 Release Features (Functional) by Status
Q1 2019 Release Features (NFR) by Status
Feature is waiting to be picked up by PO.
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.
PO analysis is complete. Stories are written and mockups have been created.
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.
Most or all stories in the feature are In Review (being tested).
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|
As noted in several weekly status reports, the Core Functional team is behind schedule. As a result, several features will not make the Q1 release. The following features have been reassigned to Q2:
Q1 2019 Spillover and At Risk Issues
|At Risk Issues||Q1 stories and features that are at risk (meaning they may spill over)|
|Spillover Features||Features originally targeted for Q1 which have been shifted to Q2 due to insufficient capacity|
|Spillover Stories||User stories originally targeted for Q1 which have been shifted to Q2 due to insufficient capacity|
The focus of Q1 2019 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 (UXPROD features) that have not yet been ranked by Chalmers. As these features are ranked, we should expect the features needed below to increase. Getting issues...
Remaining Features Needed by Chalmers to Go-Live
|Epic Link||Fix For Versions (non-archived)|
|Q4 2018||Q1 2019||Q2 2019||Unscheduled||T:|
|Allow for the creation and management of vendor records||0||1||0||0||1|
|Batch Importer (Bib/Acq)||0||0||1||0||1|
|Loan Rules and Policies||0||5||0||1||6|
|Order Materials and Services||0||1||0||0||1|
|Orders and Inventory Integration Phase 1||0||0||1||0||1|
|Receiving and Checking-in of Physical Items||0||0||1||0||1|
|SIP2: Protocol for self-checkout||0||0||1||0||1|
|Tags - Basic||0||1||2||1||4|
|Tags - Central Management||0||0||1||0||1|
|Total Unique Issues:||8||32||15||16||71|
View in JIRA
Chalmers Go-Live Features at Risk in Q1
These may be carried over into Q2 2018 (either entirely or in part)
|Key||Summary||Assignee||Status||epic link||Labels||development team|
Chalmers for Go-Live Feature With No PO
|Key||Summary||Fix Version/s||epic link|
Features Needed by Chalmers for Go-Live
Q4 2018 Release History
|Current features||Features targeted for Q1 release as of today|
|Baseline release features|
Baseline features targeted at beginning of quarter (January 14, 2019)