|Sprint 62 Retro Board|
- Victoria Rabykinato switch to monthly Retros. Make sure the virtual Retro Board is created and shared to the team to add their cards while sprints are in progress.
|Board created and shared via daily Standup Notes.|
- Dennis Bridgesto focus more on the larger workflows to work properly(and not on 1 field or 1 screen).
- Dennis Bridges to organize learning sessions on interaction between different modules.
- Aliaksei Chumakou to create stories for refactoring /technical debt required for UIORGS module. Make sure we gradually refactor legacy code to make further development smoother.
- @Team to review some more stories whenever we have some time available after Standups.
|Sprint 61 Retro Board|
- @Team should not forget to test locally before submitting PRs.
- @Team should be more pro-active reviewing PRs. One should not wait until the team is pinged in Slack to review a PR. Every dev should start their day by looking on Board and checking whether any reviews are required and provide at least one review. It can help to wrap up work faster.
- @Team should ask on Standup or in Slack before picking up an OPEN story assigned to someone else. We need to make sure the work on it hasn't been started yet.
|Sprint 60 Retro Board|
- @Team to review updates more carefully to avoid cases when code coverage drops or any other possible issues.
- Dennis Bridges to make sure the stories are ready with all the details and mockups before groomings.
|Sprint 59 Retro Board|
- @Team Merging of interrelated PRs should be better coordinated (a person responsible for coordination must be appointed, list of all PRs compiled).
Ongoing. Improvements confirmed while sprint 60-62.
- @Team Make sure that additional Bugs/Stories added last minute are safe and push back on anything that can break release.
- Victoria Rabykina Use Zoom account for a month when there are 15+ attendees on the call. Switch back to Slack when we are under 15.
|Switched back to Slack while Sprint 60 as we are now within 15 ppl limit.|
- Improve prioritization of stories in backlog. Get indication of releases (Q1, Q2).
- Dennis Bridges Clarify upcoming themes to work on while Sprint Planning.
Ongoing. Improvements confirmed while sprint 60-62.
|Sprint 58 Retro Board|
- @Team to add their names at the end of a retro item to make it easier for everyone to know who wrote it.
Ongoing. Worked well while Sprint 59 Retro.
- @Team to create new stories/bugs in Draft and assign to PO for review. PO should update and confirm acceptance criteria and move to Open for the team to review and estimate.
In progress. Statuses and descriptions were added to Acquisitions - Jira Hints.
- @Team to be more active adding cards to Retro Board.
In progress. Little improvements observed while Sprint 58-60.
|Sprint 57 Retro Board|
- @Team Before we move our story to In Review column, add some evidence of whatever was verified (screenshots, clarifications). So whoever reviews the story afterward can use that information to verify further in detail.
Ongoing. Improvements observed while Sprint 58-59 and confirmed by PO.
- @Team Keep API tests up-to-date.
- @Team Feature and code freeze to be respected by all the devs in the team and outside. Craig McNally to discuss with some external teams.
|Ongoing. Improvements confirmed while Sprint 58-62.|
|Sprint 56 Retro Board|
- @Team and Piotr Kalashuk Add sample API call and response data in appropriate MOD* tickets, so ui-team can work with API before back-end code is merged.
- @Team Delete branches after merging or closing PRs.
Ongoing. Improvements confirmed by the team while Sprint 57-59.
- @Team Brainstorm ways to spread the load on reviewing back-end stories and accepting before closing (rotation).
Ongoing. It was agreed that each sprint there will be some volunteers to help Craig check back-end stories In Review and accept.
- @Team Subtasks / Separate stories for tests linked to implementation story via "should be done together with".
Ongoing. The team agreed that ideally every story should include tests. In case it is more convenient for a dev, a sub-task for tests can be created within a story. For the modules without coverage, we need to add separate stories to create tests.
- @Team Create Template for back-end stories/bugs.
MODINVOSTO-6Getting issue details...
- preferred format was offered. It is not possible to create a specific template as the focus of back-end stories is more on content rather than on format.
|Sprint 55 Retro Board|
- @Team Add Retro cards beforehand to save time during the meeting.
Ongoing. Improvements observed while Sprint 56-57 Retro.
- @Team to better coordinate breaking changes to be merged and consider all the dependencies between modules. Be careful about incrementing versions and make sure all the related modules are ready so support the change. Follow the Pre-merge checklist to be prepared by Craig and reviewed by the team.
|Pre-merge Checklist is now available in PR template.|
- Dennis Bridges, @Team to use templates while creating UI Stories or Bugs.
|Acquisitions - Definition of Ready is updated with pre-formatted templates to be used.|
- Victoria Rabykina to balance planning to reserve some time available for any urgent issues/dependencies to be dragged into sprint. Also avoid taking a lot of successive tasks as delaying one of them delays all the chain that cannot be completed within the sprint.
Ongoing. As agreed the team should focus on 2-3 features while planning. The draft of Acquisitions - Roadmap was created to visualize the features and feature/code freezes for proper planning. Improvements observed while Sprint 57-60 as some time is reserved for working on urgent bugs and release activities.
- @Team to focus on the stories In Code Review and provide PR reviews if required before starting some new work, to avoid PRs waiting for review too long. If no progress on PR reviews - ping the team in Slack channel asking for review. Try to stick to a rule of at least 2 approves before merging a PR.
In progress. Improvements observed while Sprint 57-60.
- @Team Stories should have proper descriptions, PRs attached, clarifications on what was done to simplify the review.
|Sprint 53-54 Retro Board|
- Dennis Bridges, Craig McNally and @Team always try to break very large stories down into smaller stories/testable sub-tasks, so that testing can be done in smaller sessions. We should also try to spread the load of reviewing stories across the sprint to avoid overload at the end of sprint.
Ongoing. Improvements observed and confirmed by the team while sprint 56-59.
- @Team to always include some buffer time into future stories/bugs to work on some improvements of test coverage for legacy code.
Ongoing. Improvements were confirmed upon review.
|Acquisitions - Jira Hints page is added and shared to the team.|
- Dennis Bridges, Ann-Marie Breaux not to use sample data while testing Stories/Bugs as we have sample data issues caused by cross-module dependencies. Testing should be done on fresh orders/lines.
Ongoing. Groomings on Receiving and Checkin flow were done in Sprint 55/56. Learning sessions on invoicing were done while Sprint 57.
- Victoria Rabykina to organize back-end demos for stories with major business logic changes or wherever applicable to share knowledge across Thunderjet/Stacks/Ebsco.
Ongoing. Back-end devs demoed on Internal demos for Sprint 56/57.
- @Team to have technical discussions to happen via group chats as far as possible for the benefit of the entire team and prevents repetitive questions.
|Sprint 52 Retro Board|
- @Team introduce regular releases of modules (once per month) to get more prepared for quarterly releases and minimize risks of delaying quarterly releases.
|Done in Sprint 55. Next release planned for Sprint 57.|
- Dennis Bridges, Craig McNally, Victoria Rabykina to make sure that separate groups (Thunderjet devs, Ebsxo+Stacks back-end devs, Arvind) are reviewing backlog and estimating stories on regular basis - at least once per week. The joint Backlog Grooming meeting is to have a catch up on backlog condition and agree about next steps.
- Dennis Bridges, Ann-Marie Breaux, Craig McNally to review stories that are moved to IN REVIEW as soon as possible, so that they are closed within the sprint. In case for some reason the updates are not available for testing, inform the devs asap to double-check.
- Victoria Rabykina and @Team to be more timely arriving to Standups and other meetings. In case you cannot attend, notification should be sent via Slack to inform the team or SM and share your status. Thus, the team won't waste time waiting for the person who is not going to attend and the team will have understanding of progress of that person.
- Victoria Rabykina and @Team to estimate Bugs and any unplanned work added to Sprint on the fly as it affects the stats of the team as the initially planned work is put aside.
|Sprint 51 Retro Board|
- Ann-Marie Breaux, Dennis Bridges work on priorities for front-end and back-end devs to get the process of development more aligned. Detailed front-end user stories are helpful to understand requirements and create corresponding back-end stories. It would be more efficient if back-end development is started earlier and back-end is available when front-end stories are close to completion. Thus, we can have front-end implementation and integration with back-end within one story and won;t need separate stories for integration with back-end.
|Sprint 50 Retro Board|
|The field is added.|
- Ann-Marie Breaux to schedule the series of knowledge sharing sessions to onboard Thunderjet devs.
|3 sessions have been done + Q/A session.|
|Sprint 49 Retro Board|
- Victoria Rabykina Improve Backlog Health: organize regular Grooming meetings to identify inter-dependencies between the stories before planning.
|Regular Groomings scheduled for Wednesdays starting from Nov 7.|
|Ongoing. Forecasting of Team's velocity while planning is pretty stable for sprints 54-57.|
|Additional Priority planning meeting is scheduled for POs to work on priorities.|
|WebEx was used for recording knowledge sharing sessions.|
- Ann-Marie Breaux Schedule meeting for UI devs to get better understanding of FOLIO UX site and FOLIO design principles.
|Meeting with Filip was scheduled.|