Hi Kristin,

When it’s questions that the PO needs to answer, then I think a couple possible approaches are:

If group input is wanted, then perhaps discuss with the PO in whatever upcoming review meeting(s) you schedule for RM SIG. I’m not sure how you’ll want to organize those, since there’s lots of POs and work that relates to RM SIG: Dennis/Acq, A-M/Data Import, Owen/E, Khalilah/E, etc. Seems like it could take a few meetings.

If questions about a specific Jira that doesn’t require group input, then if you add a comment in the Jira, addressed to the PO, they can clarify for you, and then update the description if they think it would help other community members as well.

Thanks,

A-M

From: folio-rm-t@ole-lists.openlibraryfoundation.org <folio-rm-t@ole-lists.openlibraryfoundation.org> On Behalf Of Kristin Martin
Sent: Thursday, June 13, 2019 7:59 AM
To: folio-rm-t@ole-lists.openlibraryfoundation.org
Subject: [folio-rm-t] RE: FOLIO Jira review for Resource Management

CAUTION: External E-mail

Hi Ann-Marie,

Your comments make me wonder about the process here, related to Jira in general and using Holly’s spreadsheet and requested review. As a PO, would you prefer that we put comments directly in Jira or put in the spreadsheet and discuss them first within the SIG?

Kristin

From: folio-rm-t@ole-lists.openlibraryfoundation.org [mailto:folio-rm-t@ole-lists.openlibraryfoundation.org] On Behalf Of Ann-Marie Breaux
Sent: Tuesday, June 11, 2019 12:56 PM
To: folio-rm-t@ole-lists.openlibraryfoundation.org
Subject: [folio-rm-t] RE: FOLIO Jira review for Resource Management

Hi Julie,

The Product Owner (Dennis Bridges for Acq) is usually in the best position to be able to explain the differences between various features and then clean up the description to make everything more clear.

When I’m dealing with questions about a particular Jira ticket in the areas that I’m PO for, I find it most useful to have that conversation in the comments area of the ticket. That way there’s a record of the discussion, which can be particularly helpful if one ticket is eventually closed as a duplicate, or rewritten to make it more distinct from the other one.

I’m not sure how much you have worked in Jira, but if you need any help with comments, I’m happy to show you – it would just take a few minutes. Dennis is traveling today, so may not see your question in e-mail for a bit.

Now as to your question: I took at look at these, and at first glance, I’m not clear how they differ either. My guess is that they overlap or are duplicates, so one of each pair can probably be closed. Ultimately it’s up to Dennis to make that decision or to differentiate them more clearly.

Thanks,

A-M

Ann-Marie Breaux

Vice President, Workflow Management Services

EBSCO Information Services

10 Estes Street

Ipswich, MA 01938

abreaux@ebsco.com

Mobile: +1-678-427-4875

From: folio-rm-t@ole-lists.openlibraryfoundation.org <folio-rm-t@ole-lists.openlibraryfoundation.org> On Behalf Of Julie Brannon
Sent: Tuesday, June 11, 2019 12:24 PM
To: folio-rm-t@ole-lists.openlibraryfoundation.org
Subject: [folio-rm-t] RE: FOLIO Jira review for Resource Management

CAUTION: External E-mail

Greetings RM SIG,

Here are two sets of items from the capacity planning feature list that seem to overlap based on the current JIRA description and Kristin suggested I share them with this group.

UXPROD-694: CRUD Credit

UXPROD-783: Ability to create a credit

How does 694 differ from 783? The full descriptions in JIRA didn't help me differentiate these two features - could they be merged/collapsed?

UXPROD-202: Rollover Encumbrances into the next Fiscal Year

UXPROD-772: Rollover encumbrances of the ledgers funds/budgets into a new Fiscal year

How does 202 differ from 783? Could these be merged/collapsed?

Thanks,

Julie

------------------

Julie Brannon

IT Business Analyst, Library Systems and Integration Support

Duke University, 030J Bostock Library

Box 90196

(919) 613-8632

Pronouns: she/her

Duke University Libraries value diversity of thought, perspective, experience, and background and are actively committed to a culture of inclusion and respect.

From: folio-rm-t@ole-lists.openlibraryfoundation.org <folio-rm-t@ole-lists.openlibraryfoundation.org> On Behalf Of Kristin Martin
Sent: Sunday, June 9, 2019 11:49 PM
To: folio-rm-t@ole-lists.openlibraryfoundation.org
Subject: [folio-rm-t] FOLIO Jira review for Resource Management

Dear RM SIG,

Thanks for the interesting discussion on how to approach a review of Jira feature tickets to make sure that we are working on the items we all absolutely need. As we noted on Friday, although we all agree that having the SIG spent time reviewing and understanding Jiras and the connection between Jiras and our discussions, exactly how we should go about doing this is tricky. I would ask for next week Friday that everyone do the following:

Look at the spreadsheet from capacity planning: https://docs.google.com/spreadsheets/d/1eHmRKUH2mzurOLL7iaaHV65qHpvGnyN8j5YNxocMUJ4/edit#gid=805143199
Focus on the areas under Resource Management
Is there a ticket that seems confusing to you? Are institutional rankings uneven or bifurcated? Is the institutional rank significantly different from the PO ranking? Does the ticket large and unsettled but you know we’ve had SIG discussions?

I would recommend setting aside a bit of time early in the week and start sharing questions directly in the spreadsheet or via this email list. We can use the questions to build our agenda for next Friday, and see how we like this process. If we do fine Jiras that need refinement, splitting or updating, we then share the revised features with the FOLIO implementers for them to review their rankings. To do this I would probably communicate with the implementation group.

Thanks,

Kristin

Kristin E. Martin

Director of Technical Services

The University of Chicago Library

773-834-2702

kmarti@uchicago.edu

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List "folio-rm-t".
To unsubscribe from this list and stop receiving emails from it, follow this link: http://archives.simplelists.com.
To post to this group, send email to folio-rm-t@ole-lists.openlibraryfoundation.org <mailto:folio-rm-t@ole-lists.openlibraryfoundation.org%3E.
Visit this group at https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org> .

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List "folio-rm-t".
To unsubscribe from this list and stop receiving emails from it, follow this link: http://archives.simplelists.com.
To post to this group, send email to folio-rm-t@ole-lists.openlibraryfoundation.org <mailto:folio-rm-t@ole-lists.openlibraryfoundation.org>.
Visit this group at https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org> .

------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List "folio-rm-t".
To unsubscribe from this list and stop receiving emails from it, follow this link: http://www.simplelists.com/confirm.php?u=RNZIhzgRpFp0yWozAWLWBZ0apPQfuG3R.
To post to this group, send email to folio-rm-t@ole-lists.openlibraryfoundation.org <mailto:folio-rm-t@ole-lists.openlibraryfoundation.org>.
Visit this group at https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org> .