2018-05-24 - System Operations and Management SIG Agenda and Notes

2018-05-24 - System Operations and Management SIG Agenda and Notes

Date

May 24, 2018

Attendees

  • @Ingolf Kuss

  • @Wayne Schneider

  • @Dale Arntson

  • @Christopher Creswell

  • @Greg Delisle

  • @spampell

  • @Todd Wallwork

  • @Tod Olson

  • @Chris Manly

  • @Mike Gorrell

Goals

Discussion Items

Time

Item

Who

Notes

Time

Item

Who

Notes

5

Welcome

Ingolf

  • Welcome

  • Determine Note Taker: Wayne

  • Review action items: stalled

 10

Organizational

Ingolf

  • Proposal for a PO for SysOps SIG will be presented to the PC today: https://docs.google.com/document/d/1JTOPMca4qv1qDAzNYa62trKqemKQU2TpzkxhiJ8ktqI/edit - comments by Harry

  • Communication of the SysOps SIG with the developers / Role of the PO :

    • The SIG members have the skills and background to interact directly with developers on issues. SIG members report back to the group only as needed.

    • The PO can lean on information from the SIG members about the progress of JIRA tickets.

    • The PO is a promoter of the SIG's needs for development; PO communicates with the PC and other project members.

    • PO will work with @Cate Boerema (Deactivated) and @Jakub Skoczen on the prioritization of JIRA tickets.

  • Specific examples

    • LS-Tools

    • Migration tool

    • Allocating developer time for operational issues

      • Deployment mechanisms

      • Integration

      • Performance

      • Release management

  • How to use JIRA – four levels

    • App ideas

    • Epics

    • Features

    • User Stories

We can create issues at every level, Cate and Jakub will prioritize and assign. But the work of turning app ideas or epics into features and user stories is typically the work of a product owner.

The role of the product owner is to coordinate this work. It could be distributed, but is that desirable?

If distributed, JIRA story authors will need to advocate with Cate and Jakub and follow through on tickets.

Proposal: SIG members create tickets, communication with technical/PO team facilitated by PO.

Truth of the matter is a PO will not be assigned quickly. Proposal to ask for a PO now, but proceed with distributed model while one is assigned.

Dale registered a strong objection to a product owner out of concern that introducing an extra layer will impede needed conversations between the SysOps team and developers.

Voted: in favor of bringing the request for a product owner to the product council.

Future agenda item: working with JIRA

5

Identifiers on Discuss

Tod

I've posted a thought piece on Discuss to start a conversation about identifiers:

On Primary Identifiers in FOLIO

5

Ticketing System

Ingolf

Shall we bring Ticketing System idea by @Schwill, Carsten to the PC / Cate / Harry ?   Same question for LS Tools .  –   connected to PO proposal

Tabled for lack of time

5

JIRA Tickets

Ingolf

Open JIRA Tickets realted to SysOps issues  –  connected to PO proposal

Tabled for lack of time







next week holiday for Ingolf (Corpus Christi), Dale will convene.

Action Items