Skip to end of banner
Go to start of banner

Core functional - Retrospective / Action Plan

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 36 Next »

Ongoing improvements
Next sprint improvement action items
Sprint 67 Retro Board
  • Sprint retrospective agenda should be extended to cover sprint review topics:
  • extra items added to sprint during the sprint
  • wrong estimations that did not include some aspect
  • raise discussion about carry over items 2+ times

along with regular retro discussion. Assignee: Oleksiy_Lemeshko


  • Below tasks assignment approach should be followed by Core: Functional team members:
  • look to the To Do column of Core: Functional Scrum Board in the current sprint for work to do before considering other stories. Please consider priority/order
  • raise with Lead PO and/or SM if you're about to work on an item that is not in the sprint. Stand-up is workable channel
  • if there is nothing for you in To Do list feel free to check highest backlog item that was previously refined (has estimation). Mention your intention during the stand-up


  • Core: Functional team members to notify Tech Lead/SM about OOO plans 

Above improvements will be added to Ongoing improvements section during next retrospective 

Sprint 61 Retro Board
Sprint 60 Retro Board
Sprint 59 Retro Board
  • Oleksiy_Lemeshko to check with other teams what BE style guide is used. Suggest google if not defined yet
  • Team members to come out with the list of tech debt items by Tuesday, the 26-th. Oleksiy_Lemeshko to remind during stand-ups
  • Oleksiy_Lemeshko to setup a meeting where CF team would generate release plan
Sprint 58 Retro Board
  • Other teams breaking changes to be brought up to CF team attention by Monday, the 6-th day of each sprint. Oleksiy_Lemeshko to communicate it during SM meeting next Tuesday
  • Oleksiy_Lemeshko to clarify the scope of PR review activity and level of CF team responsibility
  • Oleksiy_Lemeshko to bring up on SoS meeting the size of PRs
  • Investigate check style integration (BE): Matt Reno - spike, Oleksiy_Lemeshko to raise it with CP team
Sprint 57 Retro Board
Sprint 56 Retro Board
  • Oleksiy_Lemeshko to split retro wiki page into two sections: ongoing improvements and next sprint improvement actions items
  • Oleksiy_Lemeshko to arrange meeting for team DoD discussion once test coverage fix prerequisite is resolved (moved to next sprint)
  • Oleksiy_Lemeshko to remind Marc Johnson to figure out better approach of handling crossteams PR reviews/coverage fixes/etc (moved to next sprint)
  • Oleksiy_Lemeshko to define CF team volounteers for specific modules "ownership" in terms of PR reviews
  • Oleksiy_Lemeshko to continue with ui-only groomings
  • Oleksiy_Lemeshko to provide Peter Murray team meetings schedule in order to create zoom meeting using paid accounts
Sprint 55 Retro Board
  • No labels