2020-05-06 Meeting notes

2020-05-06 Meeting notes

Date

May 6, 2020

Attendees

  • @Mike Gorrell

  • @Tod Olson

  • @Craig McNally

  • @Jakub Skoczen

  • @Mark Veksler

  • @Marc Johnson

  • @Ian Ibbotson (Use this one)

  • @Zak_Burke

  • @Ian Walls

  • @spampell

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

15 min

Tech Leads Retrospective

@Craig McNally

Review 2020-04-23 2020 Q1 Release Retrospective and decide if TC has any actions. two main themes:

1) Improve communication - what's happening (increasing data size dramatically in bugfest environment), what's the process (what is the bug fix release process for bugfest) and what are the expectations from teams (upgrade scripts part of Definition of Done? Are teams expected to compare DB definitions fresh and post upgrade to confirm consistency)?

2) We need more DevOps capacity - need to service many teams needs for access to logs, creation of various environments, apply patches/fixes, push CI/CD jobs, etc.

Note not having enough DevOps capacity has a direct impact on teams' ability to deliver in the current and future quarters. Anecdotally cost many teams a sprint of more of work, and you could argue that many of the 50 items in the Hotfix were partially the result of lack of resources (also related to need for improved communication).

15 min

 Review/approve Release numbering recommendation

TC 

Release numbering the Platform. Latest (final?) version to discuss with FOLIO implementers and present to Product Council: 

https://docs.google.com/presentation/d/1QmX-Jl5wT4GQgW7uFk08FPeAX_6v6zzvXX8ZQT5VG4g/edit#slide=id.p1

30 min

New/revised backlog items 

TC

Describe, prioritize and schedule further discussions:

  • pr preview updates - CI/CD environments being discussed 

  • tech debt - To review DEBT project, also Marc Johnson reviewing "old" bugs (i.e. open more than 365 days); some may be Tech Debt items.

  • arch. blueprint items  - Discussions are ongoing. Get summary of discussions next week.

  • start prioritizing Q3 work for the core:platform team - want items above to be far enough along to influence what items make it onto Q3 plans.