Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Since this is a new area, there is a lot to discuss and team would like to be sure they have all questions answered given folks will be out over the holiday
Will allocate 40% of story points to bug fixing
New process will ask teams to dedicate 40 - 50 % of story points to bug fixing until all p1, p2 and p3 bugs are closed. Vega, Concorde and Folijet will also help work through the Core Functional bug backlog
Focus to start would be ui-only fixes as back-end bugs are more involved (often require architecture decisions, are breaking changes etc) and the defect priorities need to be reconsidered for back-end bugs
Cap planning team working to get initial Q1 planning together by end of week
A group of modules didn't meet the December 4th deadline which means that verifying and branching was delayed until Monday morning. Most of them has been released until Monday morning and are included in Q4 but 3 modules had to be removed to allow for the release succeed: mod-patron, edge-patron, edge-sip2. These will be included in the coming days.
A group of modules didn't meet the December 4th deadline which means that verifying and branching was delayed until Monday morning. Most of them has been released until Monday morning and are included in Q4 but 3 modules had to be removed to allow for the release succeed: mod-patron, edge-patron, edge-sip2. These will be included in the coming days.
UXPROD-2173 Display Effective Call Number Throughout Requests App
POs will be adding priorities to their spillover MVP features. Higher priority features are those that would require more testing and training (assumption is that those should be completed first)
Capacity planning group will synthesize this PO priority data and the updated team allocations to generate a plan for Q1
Prioritizing wrapping up development on in progress features and priority bug fixes
There will be significant spillover (52 issues currently - see table on Q4 2019 Dashboard)
In addition to features that will spill over in their entirety, many In progress features will have to be "split" meaning there will be partial carry-over
For Core Functional, the following features: will need to be split:
Many (most?) features currently "In progress" are likely to need to be split.
In some cases, a good thin thread has been implemented in Q4 and what is left is lower priority and/or small in scope
In other cases, a sizeable amount of priority development will need to be split and carried over.
Often the remaining development can be completed in the Q4 development period (just too late to make the actual release)
The cap planning group is:
Evaluating the items that have been tagged by POs as spillover to see which are the highest priority for the 2020 cohort (including Chalmers). Holly is following up with POs on features that don't have high implementer rankings to better understand their priority. These usually have explanations e.g. they represent thin thread workarounds for other features the implementers really need.
Gathering info on what the development capacity will be in Q1
UI developers are working through many Inventory search and filter enhancements, wrapping up Reorder request queue feature and fixing priority bugs (also struggling with integration tests)
The team feels we are close to getting being over the hump, at which time development should accelerate
Core Functional folks had a good meeting last week with Jakub to discuss plans for Inventory search and filter and we have a clear plan for some long-awaited features such as:
The number of mysterious circulation issues being reported by Chalmers has virtually stopped
It looks like there will be more spillover features this quarter than we have seen in the past and the PO have gathered their thoughts on why that may be. Issues include team turnover and vacations, dependencies between features, underestimated features and late requirements.
POs and Anton discussed the desire to capture bug reports from broader community, as implementers are beginning to test in earnest. Currently thinking about setting up a special project for this purpose. More conversations are needed and we've submitted as a topic for Wolfcon.