Action Plan | Notes |
---|
| |
| Victoria_Smelovahas agreed with Anton Emelianov (Deactivated)that he will create a doc with description how to handle multi releases in parallel |
| |
| Done |
| |
| |
|
Ongoing |
|
Ongoing |
|
Guide updated | |
| To be revisited after R1 |
|
Features for working on tech debt were created for R3 | |
| "acq-dev-grooming" label was created and "Grooming" quick filter was added to Scrum Board |
|
| Spike is created and estimated - MODORDERS-427 Currently blocked by DevOps task. |
| Ongoing. Example:
|
| ||||||
| Done. | |||||
| Done. | |||||
|
Communicated to the teams |
|
| |
| The question was raised to Cate and POs and will be further discussed outside the team. |
| Ongoing. Improvements confirmed after S93 |
|
| Improvements confirmed after Q3. |
| Improvements confirmed after Q2. |
| Improvements confirmed after S96. |
| Improvements confirmed after S96; requirements were updated in uxprod features while implementation as some aspects were learnt by the dev team. |
| Thunderjet - Jira Flow was updated. |
| Thunderjet Releases dashboard was created to visualize all planned releases and their dependencies |
| Done |
| Regular meeting is scheduled in Teams. |
|
| Ongoing. Improvements confirmed after Sprint 86. |
| Ongoing. Improvements confirmed after Sprint 87. Spillovers are reduced. |
| A Grooming wiki page created with a filter to track stories ready to be groomed. |
| The team agreed to timebox the spikes and then discuss the progress to decide whether we need to proceed with some follow-up spikes. The approach was tested while Sprint 86. |
| Ongoing. Sharing some videos of end-to-end flows can be an option. |
| Some time was reserved for urgent issues while planning release sprints for Q1. Thanks to that the team managed to add some additional issues without failing Completion Ratio. |
| Improvements confirmed after Sprint 91 |
| Improvements confirmed after Sprint 86. |
|
| Ongoing |
| Improvements confirmed after Sprint 82. |
| Updated schedule was created and reviewed/approved by all POs and SMs. |
| In progress. Regular meeting is scheduled for Dennis, Craig, and Ann-Marie. |
| Separate channel for BE devs to coordinate PR reviews was created. |
| Improvements confirmed after Q4 release. |
| Ongoing. Mentioned in daily notes |
| Ongoing |
| Confirmed as improved after Sprint 81 |
| Kimie was invited to some meetings on request. |
| Story created for DevOps.
|
API test strategy is outlines and will be rolled out across folio | ||||||||
| Ongoing. Improvements confirmed by the team while sprints 69-76. | |||||||
| Ongoing | |||||||
| confirmed after Q1 2020. | |||||||
| Ongoing. The spreadsheet was updated on time for Q3.2 and Q4 releases. | |||||||
| Story created for DevOps.
|
|
| Ongoing. No issues while Q3.2 and Q4 releases. | |
| Ongoing | |
| Ongoing. No issues observed while Q3.1 delivery. | |
| Ongoing. Successfully done while Q3.1 release. | |
| Done. | |
| Ongoing. Improvements observed while Q3.1 delivery. | |
| In progress. Improvements confirmed by the team while sprints 67-76. | |
|
Ongoing. | |
| Confirmed as helpful. Should be organized on demand. |
| Ongoing. |
| Planning was adjusted according to separate coefficients for Back-end vs Front-end. |
| Board created and shared via daily Standup Notes. |
| |
| |
| Ongoing. Creation of stories confirmed while sprint 63-68. |
| The team decided to add additional Grooming meetings instead of some Standups. |
| Ongoing. |
| Ongoing. |
| Ongoing. No issues observed while Sprint 62-69. |
| Ongoing |
| Ongoing |
| Ongoing. Improvements confirmed while sprint 60-62. |
| Ongoing. Improvements confirmed while sprint 60-68. |
| Switched back to Slack while Sprint 60 as we are now within 15 ppl limit. |
| Ongoing. Improvements confirmed while sprint 60-69. |
| Ongoing. Improvements confirmed while sprint 60-62. |
| Ongoing. Worked well while Sprint 59 Retro. |
| Ongoing. Statuses and descriptions were added to Thunderjet - Jira Flow. |
| Ongoing |
| Ongoing. Improvements observed while Sprint 58-59 and confirmed by PO. |
| Ongoing |
| Ongoing |
| Only UIF module has the coverage of <80% due to legacy code. There is no sense investing time into increasing coverage now as the module is planned to be reworked and coverage will be added while working on stories. All the other modules are >80% covered. |
| Ongoing. Improvements confirmed while Sprint 58-62. |
| Ongoing. Improvements confirmed by the team while Sprint 57-59. | ||||
| Ongoing. It was agreed that each sprint there will be some volunteers to help Craig check back-end stories In Review and accept. | ||||
| 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. | ||||
| Ongoing.
|
|
| Ongoing. Improvements observed while Sprint 56-57 Retro. |
| Pre-merge Checklist is now available in PR template. |
| Acquisitions - Definition of Ready is updated with pre-formatted templates to be used. |
| 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. |
| In progress. Improvements observed while Sprint 57-60. |
|
| Ongoing. Improvements observed and confirmed by the team while sprint 56-59. |
| Ongoing. Improvements were confirmed upon review. |
| Thunderjet - Jira Flow page is added and shared to the team. |
| Ongoing. |
| Ongoing. Groomings on Receiving and Checkin flow were done in Sprint 55/56. Learning sessions on invoicing were done while Sprint 57. |
| Ongoing. Back-end devs demoed on Internal demos for Sprint 56/57. |
| Ongoing. |
| Done in Sprint 55. Next release planned for Sprint 57. |
| Ongoing. |
| Ongoing. |
| Ongoing. |
| Ongoing. |
| Ongoing. |
| Ongoing. |
| The field is added. |
| 3 sessions have been done + Q/A session. |
| 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. |
| Meeting with Filip was scheduled. |