Thank you for organizing this Kelly, I think your proposed framework sounds good and I really like that this will begin to connect with PO's for the related functional area as development is occurring.  Either approach - checking the validity of each epic first or taking a few epics through the framework - would work for me.   I'm not sure if this is already captured, but should we also add a column, maybe for our own reference, to cluster the epics into functional areas of the system, much like when we were brainstorming?   This might help us focus on familiarizing ourselves with functionality related to several epics to address at once before moving on. 

Thanks,

---Noah

Noah Brubaker PALNI Associate Director (317)721-8198 | nbrubaker@palni.edu | www.palni.edu c/o Irwin Library, 4553 Clarendon Road, Indianapolis, IN 46208

On Tue, Sep 17, 2019 at 1:02 PM Kelly Drake <kelly@flo.org> wrote:

SIG members,

As David emailed earlier I'd like to take tomorrow's meeting to talk about the outstanding Consortia JIRAs.  A few PO's have reached out regarding Consortia requirements for various JIRAs and it would be good to provide better answers than are contained in those (often confusing) tickets.   While we had hoped to table those until we had completed Cross tenant, unmediated requesting, it appears that now is a good time to start organizing the JIRA's. Before doing that I propose that we take a few minutes to establish a framework for developing and implementing Consortia requirements within the FOLIO community. From there, I think, the task of organizing and clarifying existing and potential Consortia-related JIRAs will be more straightforward.  I hope, at this meeting to get some general guidance, so that I can present a general framework to the POs at their 11:00 meeting - an hour after this meeting ends.   

As it is, we've already taken the first step toward organizing  existing JIRAs by differentiating single tenant vs cross tenant functionality. We've also begun distinguishing between "Central Office" functions and those performed jointly between consortia tenant.  For instance cross tenant unmediated requesting is generally a library to library function.  On the other hand, something like patron uploads, could be performed by a Central office. 

What we have not directly addressed, is how to develop Consortia stories that interact with existing FOLIO functionality.  This I believe, is the next step. As we've noticed with unmediated cross-tenant requesting, a great deal of what we have specified overlaps with what FOLIO already does. Identifying and familiarizing ourselves with that functionality (perhaps with input from the FOLIO SIG and PO) seems to be a good next step. Following that we could develop the Consortia features, and then collaborate with the FOLIO SIG and PO to complete the specification.  

What are your thoughts on the following proposal:

Proposed Consortia function development framework

1. Determine whether or not the function is cross tenant, or single tenant
2. Determine whether the function is performed by the Central Office or jointly among libraries
3. Identify and become familiar with related, existing FOLIO functionality
4. Draft specification
5. Collaborate with functional PO for completion of specification. 

Attached is a spreadsheet with the existing Consortia JIRAs.  Perhaps a way to test  and improve the framework would be to review these Epics?  Or maybe, for now, we just want to indicate whether or not the epic is valid, and or a Central office, or joint library function?

Anyway -  we'll go over all this tomorrow, I just wanted everyone to have a heads up and time to think about this and discuss issues beforehand if you want to.  

Looking forward to a lively meeting!

-- 

Kelly Drake

Project Manager

kelly@flo.org | Conference calls: https://zoom.us/j/9606207016

To unsubscribe from this list please go to http://archives.simplelists.com

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=gpXs7VCzNLrULI0RJY4SsllK3QpUxIp4