/
2021-03-19 Retrospective Spitfire

2021-03-19 Retrospective Spitfire

Mar 19, 2021

 

Date

Mar 19, 2021

Participants

@Oleksii Petrenko @Natalia Zaitseva  @Denys Bohdan @Pavlo Smahin  @Владислав Велицкий @Dima Tkachenko @Sobha Duvvuri  @Yuliia Dovhal

 

Retrospective

 

What did we do well?

  • Complete deriving new quick mark records

  • Quick mark development for R1 2021 is finished

  • Thank for @Yuliia Dovhal for short-cut work

 

What should we have done better?

  • Have better communication with Folijet team regarding data import changes

  • Dependency between data import modules are not transparent 

  • Provided braking changes at last minute should be communicated with affected teams by email

  • Request for FOLIO DevOps team was not resolved and not taken in to work

  • DevOps team workload is not really helpful to development work

  • Process of getting logs from reference env is not smooth and required DevOps work

  • OOM is still occupied and we need to decide how to manage required and provided memory. Only 60% of memory is occupied by JVM.

  • Need to prepare load tests for our modules to get understanding of required memory.

  • Not let Dima GO

Actions

 

February 2021

RTL tests bring more complexity and additional code refactoring to eHoldings → All required refactoring effort should be visible and should be added to Jira → @Denys Bohdan
Spring improvements will be part of team work→ Conduct meeting with people which are interested in Spring and ready to assist with required changes → @Oleksii Petrenko  

January 2021

Work on improvement of integration tests
Spend more time for testing 

December 2020

Password development took longer than usual. Are there ways for the entire team to better understand complexity and level of effort to help with backlog prioritization? → Break down all tasks and not hide non-functional work at functional stories → Team
Several issues has been identified at Honeysuckle, need to verify clean setup also → @Oleksii Petrenko
Add more resources to scratch env → @Oleksii Petrenko
Verify multi tenancy during release preparation period → @Oleksii Petrenko  

November 2020

Caused additional challenges with rancher env setup → Reach out to @Stanislav Miroshnichenko
Not clear how to work with permissions (Workaround is used for now) → @Stanislav Miroshnichenko

October 2020

DT - In general module releases went well, but one issue (with logging) was not payed attention to immediately. This led to additional patch releases of several modules/libraries - Move to Release retrospective → @Oleksii Petrenko
Additional time is required for get practice with Rancher for successful roll out → Team
Rancher service should put some notifications regarding resources stopping and allocation. Reach out to @Sergiy Vysotskiy and @Stanislav Miroshnichenko → @Oleksii Petrenko

August 2020

50% Validate prepared stories quicker when it is deployed to Snapshort environment → @Khalilah Gambrell @patty.wanninger
Issue with MOD-USER-IMPORT: Expectation of user is contradict with team's one
Validate requirements by User Management SIG group or PO(Ian Walls) from MOD-USER-IMPORT before presenting them to the team → @Khalilah Gambrell

July 2020

Bugfix release cause misunderstanding when working with different jira projects and different git projects.
Post new process instruction to Spitfire channel
Need stabilize release process

June 2020

Prepare possible plan for extending current testing approach → @Denys Bohdan @maksym_dryha @Владислав Велицкий  
Verify affected areas manually → Team
Report issues to stripes team while development → Team
Check all acceptance criteria while dev testing → Team, @Khalilah Gambrell
Sync with BE team and dependency detection → Team
Part of definition of done (Include accessibility testing to testing activities by FE team) → @Oleksii Petrenko
Run accessibility checker more frequently and include it to CI pipeline (Run once in the sprint by FE team) → FE team
Clarify more carefully hidden scenarios in acceptance criteria → Team, @Khalilah Gambrell
Create stories more carefully to avoid situation that we missed some at the end → Team, @Khalilah Gambrell
Include to release preparation plan interface update for 2 weeks before release deadline (Bump up latest version of interfaces were too later) → @Oleksii Petrenko