15 | Finish the remaining Jira ticket review | Dennis | Finished this today!
https://folio-org.atlassian.net/issues/?filter=13150 What kind of a dashboard would we like, so we could see what’s happening at a higher level (what’s moving forward, what isn’t…) |
25 | Planning for Prioritization For features that are already assigned to a release, should we be doing anything else to support their development? Getting a better understanding of the lifecycle of an enhancement request (how does it get created? prioritized? picked up?) How are other SIGS prioritizing their work? Anyone doing a really good job? Can we just copy their workflow? Understanding how voting in Jira works (what are the points values? What does that impact?)
| Dennis/All | We’ll get through as many of these as we can this session – ideally at least 1 or 2 but we’ll see. For features already assigned to a release:
More SIGs are operating with POs of those domains to participate in testing. UATs are announced, users test in a prerelease environment, sometimes a bit unstable. Meant to collect feedback on the feature with time to fix problems before it’s actually released. Huge way for SIG to contribute to improve quality of FOLIO releases. Explanation of Ac UAT page and feedback form. UAT’s move fast! Sometimes not completely documented, and sometimes bugs in the environment. They are partially testing for how intuitive the feature is.
Also, bugfest is hugely important, and some fatigue is being seen.
Sometimes PO comes back with designs with more questions, asks for more use cases, during development. Lifecycle of an enhancement
Have started with requirements topics document. Folks come to a SIG with an enhancement request, add to topics list. Discussion about use cases. End up with a Jira ticket, often in form of a story. Who creates the tickets? Often Implementation folks/PO for that module. Goal is to have a discussion about that request with community. Comment on the ticket, more use cases, more discussion in SIG.
How does it get prioritized is a more difficult question, has changed over time. Someone from PO should talk more about this topic, what are they still supporting. Voting is now used, click on the “vote” icon in the Jira ticket (thumbs up icon). Any logged in user can vote once. Points method of voting was a specific initiative, not used anymore. But on older tickets this might still get looked at. PO aligns mandates they are driven by (whoever funds them!!!!) with the needs of the community. e.g. Serials app paid for by GBV and Owen (PO) balanced their needs with what general community needs. Teams look at backlog if they have time for a ticket or two. Libraries fund development.
If you’re hosted, contact vendor to get something started. Or start in appropriate SIG or PO. SIG best because more discussion occurs and easier to write good ticket(s).
|