/
2016-01-14 User Advisory Council Meeting

2016-01-14 User Advisory Council Meeting

Feb 08, 2016

Date

14 January 2016

Attendees
 

Goals
 

Discussion items

Time
Item
Who
Notes

 

Roll CallJulie Patton 
 Program UpdateJulie Patton for Brad Westbrook

    1. We had a light period of activity between the last UAC meeting on 12/14/2015 and this one today due to the winter holidays.  In effect, this report is only for about 11 working days.

    2. Development

      1. 11 user stories were delivered for sprint 19, but only four were tested, of which three were accepted and one was rejected.  Rather than try to complete sprint nineteen, we have decided to merge its contents into the backlog for 2016 Sprint 1.

      2. We have made substantial progress in transitioning the development process to the new cycle and to Agile boards now present in Jira.  Presently we are engaged in making sure all epics are represented as epics and their story members are properly linked.  We have constructed a “first draft” of the backlog for the 2016 Sprint 1.  This will be reviewed by the Prioritization subteam prior to that sprint commencing.  We are also in the process of scheduling orientation and first meetings for the prioritization subteam and the testing subteam.  The first scrum meeting is now scheduled for late Monday afternoon, Feb. 1.

    3. Documentation:

      1. Christine Di Bella has outline the documentation that needs to be done for new container management functionality, and she and I will be address that in the next few weeks.  We intend to use the documentation subteam as our reviewer/editor.

    4. Workshops:

      1. Nancy Enneking presented a two-day Basics ArchivesSpace workshop at Texas A&M University Corpus Christi (TAMU-CC) on Dec. 14 and 15.  That workshop also included staff from Texas A&M University Kingsville.  Bergis Jules was present as new trainer-in-training.

      2. Bergis Jules and Lisa Calahan presented a workshop at Tulane University on Jan. 11-12 for staff at Tulane, Nicholls State University, and LSU.

 Sub-team Reports  
 Feature PrioritizationJulie Patton

      1. Worked through the end of sprint 18-19, unfinished from sprint 19 will merge with 2016 sprint 1

      2. Looking ahead to splitting into features prioritization and testing
 DocumentationLinda Hocking

      1. 4 screencasts up on documentation page now

      2. Discussing how to invite contributions from users

      3. Working on Yale container plugin documentation
 ReportsNancy Enneking

      1. Some testing on reports in 1.4.2 dev ver 18

      2. Running better but still some issues

      3. Discussion about reports issues

        1. Stored procedures causing problems on backend

      4. May push the export for certain fields for user manipulation in excel (very early stages of discussion)
  Split of the Features Prioritization subteamGordon Daines

    1. Idea to split Features Prioritization into Development Prioritization subteam and Testing subteam from November developer's meeting

      1. Features prioritization has enough work to create a separate team without responsibility for testing

      2. Discussing how to move the processes to two separate teams esp. with regard to longer sprint cycle

      3. Julie Patton leading development prioritization subteam

      4. Miloche Kottman leading testing subteam

      5. Some draft charge documents in the works already

      6. Hoping to establish a standard protocol for testing procedures
    

Action Items: