Retrospective Win4Win Relounch

Reason for the event:

Shift the date of the launch

Date of the event:

07.11.2024

Participants:

Anna Potiiuk, Anna Aksonenko

 Background.

List the events leading up to the incident in chronological order.

The launch was scheduled for October 30.

A week before live, during a call with Chiara, it was agreed that win4win would not only like to keep the content of the live site but also transfer the content that had been added to the stage.

Accordingly, we agreed that we would be provided with a file with a list of what exactly should be transferred from the stage to the live site.

28.10 Anna Potiiuk reminded about this file – https://prnt.sc/vRHSuuvB5Ndl
29.10 once more – https://prnt.sc/5p1rm_GhWZ46

periodically checked whether the file was available

 Issue

Describe how the changes you made did not work correctly. If possible, provide a visual representation of the data.

File https://docs.google.com/document/d/10Fov1h3Hl6QCJNdKmg3e_j9a4UgyOEh7QqVAiflCEO0/edit?tab=t.0

After analyzing the file, it was found that it would take more time to transfer so much selective information, and therefore we would not have time to go live on 30.10, which was reported to the client.

I received the file only on 30.10 in the morning (i.e. on the day of the launch) – https://prnt.sc/PISHs_-iILoF

I received the full information only on the day of the launch, consulted with the team leaders, made a plan on how to transfer at least some of the information, but the information was still transferred incorrectly (mismatch of post and media IDs on production and stage, etc.)

After that, it was decided to transfer the information completely manually (to prevent incorrect data on the live page after such transfer), which took much longer than estimated.

 Impact

Describe how the incident affected internal and external users.

Since the client requested that launch should take place at least on October 31, the developer had to work literally 24/7.

Over work during non-working hours

Over work during non-working hours

Response.

Report who responded to the incident, what actions were taken, and when. Indicate any delays or obstacles to the response.

PM and the developer agreed on an action plan and PM informed Chiara about the shift of the live date to 31/10.

Chiara offered her help as well, but it was not needed at this stage.

I supported the developer, communicated and helped with content tasks.

With the help of PM and tech leads, I made the transfer and checked the correctness of the data

 Resumption of work

Launch took place on October 31.

 Identify the root cause without blame

Identify the ultimate root cause and describe what needs to be changed (without blaming anyone) to prevent similar incidents from happening in the future.

Late received transfer requests

Late received transfer requests

 Lessons learned.

Describe what you learned, what worked, and what could be improved.

Ask for these requirements more insistently, emphasize the importance of providing it, and warn that if you don’t provide the file at least 3 days before the luncheon, you risk not being able to go live on time.

When working with websites that are already launched, immediately before the estimation, discuss with the customer what data should come from the old site, what data should come from the new site, and what the final result will look like.

At least 3 days before the launch, get the final requirements, write a migration plan, stop development and final testing.