Page Comparison

•  

  Developers and POs need to think about release deadlines differently. Dev deadline should actually be 3 days before (to give POs time to review and reopen, if needed). Oleksiy_Lemeshko: Needs to be raised as project question. Should we add additional milestones?

  
  

•  More frequent releases? Would need to lower cost of releasing (e.g. bugfest testing). Could we automate bugfest? Also, some features will only be half-done when you want to release. We could develop the capability to turn the feature off. FOLIO is not setup for that at the moment.
•  Even if we set dev deadlines earlier to avoid having unfinished work merged at time of release deadline, we know we will sometime need to re-release modules or patch modules when unfinished work comes in.
•  

  Marc will bring up the news thing again with tech leads. People should put titles and good descriptions on PRs etc.

•  Could use the release JIRA issues to discuss release dates as long as the right people are watching the JIRA
•  

  Other front-end devs from Core Functional could help Zak with releasing modules

  Same for backend modules

  Don't want to scatter this to the wind but there is value in spreading knowledge somewhat. Especially in case Zak or Marc is out. They could also serve as escalation point if there are problems.

•  We could do some releases part way through the quarter (not to be used by anyone - kind of like a practice release). Will reduce the change log work needed at the end.

•  Oleksiy_Lemeshko to check with POs the list of stories for forthcomming refinement

•  Cate Boerema (Deactivated) to raise with capacity planning group the situation with CF team involvement in helping other teams
•  Marc Johnson and Oleksiy_Lemeshko to raise following topics with tech leads (Marc) and during SoS (OL)

• define who is responsible for shared parts of a system: stripes-core, stripes-connect, etc
• define who is responsible for approving the integration of a new module
• define a mechanizm of keeping community informed about new module is comming

•  get back later to "how to make it easier for a developer to run ui regression test suit". Oleksiy_Lemeshkoto remind during next retro
•  development team to delegate when possible
•  development team to take notes on a ticket during grooming making sure that scenarios make sence
•  development team to Raise any unclarity in US with PO or Tech Lead

•  Oleksiy_Lemeshko to setup slackbot reminider about stand-up updates provision
•  When putting a backend story In review, check to see if it was blocking anything and unblock that issue (e.g. CIRC-416 )
  Also please inform the world (core-functional slack channel :) ) about resolved dependency/prerequisite

•  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 

•  Oleksiy_Lemeshko to suggest new retro format

•  Oleksiy_Lemeshko to setup a meeting where CF team would generate release plan

•  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

•  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

•  Magda Zacharska / Oleksiy_Lemeshko Check with Anton Emelianov (Deactivated) the state of contract testing approach implementation across the project
•  Magda Zacharska Define the current state of Postman coverage
•  Oleksiy_Lemeshko / Marc Johnson Prioritize the efforts based on 1 and 2 outcomes by raising with Cate Boerema (Deactivated)
•  

  Marc Johnson / Oleksiy_Lemeshko to discuss on Monday call with Marc/Jacub/Cate/OL : cross team work, closure of backend stories approach, minimalist PR reviews

•  Oleksiy_Lemeshko to arrange meeting for team DoD discussion once test coverage fix prerequisite is resolved
•  Oleksiy_Lemeshko to remind Marc Johnson to figure out better approach of handling crossteams PR reviews/coverage fixes/etc

•  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

•  Oleksiy_Lemeshko suggest UI only work backlog items for sprint backlog in order to ballance BE and FE workload and ensure that BE and FE efforst for same US are properly lined up during planning
•  Aditya matukumalliJakub SkoczenMagda ZacharskaMarc JohnsonMartin TranMatt RenoMatt ConnollyMichal KuklisNiels Erik NielsenRyan LaddusawZak Burke to provide inputs re DoD on Core:functional - Definition of Done
•  Oleksiy_Lemeshko to arrange meeting for team DoD discussion. Should be done during rhe first half of S56
•  Magda Zacharska to add USs to backlog re integration testing