2020-07-17 Retrospective Spitfire

2020-07-17 Retrospective Spitfire

 

Date

Jul 20, 2020

Participants

@Oleksii Petrenko @Khalilah Gambrell @Carole Godfrey @Dima Tkachenko @Natalia Zaitseva @Pavlo Smahin @Denys Bohdan @maksym_dryha @Владислав Велицкий 

 

Retrospective

 

What did we do well?

  • Enough work for FE and BE. Backlog is in the good shape

  • Team is working well. Communication inside the team is working as good Swiss watch

  • Working together on reference environment configuration

  • Great job with Custom Fields, Single tenant with multiple KBs

  • UAT shows well received features

  • BE team show patient for backlog level

  • BE team is working in different projects

 

What should we have done better?

  • 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

Actions

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