Theme

Category: PM Team Space

  • Retrospective findings

    Project: Ascet Shipping

    Team: PM: Givi Dzandzava; FE: Ihor Havrilenko; BE: Artur Bulan; QA: Artem Makarov; Team Leads: Alec Shpigar, Pavel Truhin

    Link to the Retrospective document – Retrospective

    Висновки

    Опис

    Відділ

    Виділяти більший час на аналіз дизайну

    Розглядати дизайн з позиції один одного, обговорювати кожен блок як фічу, а не поверхневий огляд сторінку

    TEAM

    Розглядати дизайн з позиції UI/UX, більше власних пропозицій з приводу покращення дизайну та функціоналу

    Створити підхід ніби ми кожен сайт розроблюємо для себе і ми будемо основними користувачами. Надавати більше пропозицій до дизайну, навіть, якщо не ми його створювали. Критично осмислити кожен функціонал, передбачити його варіації та донести це до клієнта, запропонувати найкращі способи імплементаціх

    TEAM

    Створити уніфіковану структуру тасок

    Затсосовувати уніфіковану структуру тасок, щоб пришвидшити вникання у таску

    PM PROCESSES

    Писати рекомендовані розміри та формати медіафайлів для блоків, зробити адмінку біль user friendly

    Можливо додаткові description з зазначенням розмірів зображень у блоки, де потрібно вставляти медіафайли. Інші способи зробити адмінку більш User friendly

    DEVELOPEMENT PROCESSES

    Якщо міняємо розробника, робимо нову (внутрішню) естимацію

    Кожна особа має сама оцінити скоуп роботи. Бажано фіксувати цей показник окремо

    PM PROCESSES

    Додавати репорти до виконанї таски/баги

    Відноситься до фіксу багів. Треба створити щось по типу структури тасок. Можливо наступне: 1. Problem description (технічний опис, бо функціональний і так має бути наявний у багу) 2. How solved (опис рішення) 3. Screens 4. Links

    DEVELOPEMENT PROCESSES

    Додавати original estimate у таски

    Додавати у відповідні поля у тасці Jira

    PM PROCESSES

    Створювати блоки за назвами блоків з естимації

    Під час розгляду дизайну з командою, дати назву блокам, якої варто притримуватись на етапі розробки

    DEVELOPEMENT PROCESSES

    Розробники мають самостійно активно підключати Тім лідів

    Не занурюватись у виконання таски надміру, чітко розуміти, коли вже час звернутись за допомогою до Тім лідів

    DEVELOPEMENT PROCESSES

    Слідкувати за документом естимації

    Слідкувати за різницею естимованого та витраченого часу у відповідних полях таски

    DEVELOPEMENT PROCESSES

    Next project:

    Project: Swisskrono

    Team: PM: Kate Hvozd ; FE: Oleksii Reshetnyk Dmitriy Rogkov (Unlicensed) ; BE: val.b (Unlicensed) Anna Aksonenko ; QA: Artem Makarov Illia Bilyk (Unlicensed) ; Team Leads: Alec Shpigar , Honcharuk Oleh Pavlo Trukhin SysAdm/D.​OPS: Roman Kliuiko SEO: Anna Nikitina (Unlicensed) . (PM help Givi Dzandzava (Unlicensed) Andrii Kupriianov )

    Link to the Retrospective document – Retrospective

    Висновки

    Опис

    Відділ

    1. Unique blocks separately on the design (if possible) + desk and mob in one board

    Ask designer to prepare the unique blocks separately on the design if there are 2+ pages that share the same blocks. (PM)

    PM PROCESSES

    1. More carefull with complex functionality estimation

    Be more carefull with complex functionality estimation

    • (like map), ask client more questions and add more risks if it’s needed. In the estimation file add the full description of what was estimated with the note that “additional requiremnets will be estimated separately”) (PM)

    • Backgrounds – more detailed exploring and estimation

    PM PROCESSES

    1. Requirements in 1 place

    1 main file should include all the blocks descriptions + copy description in Jira task (Artem Makarov, Dima Rogkov)

    PM PROCESSES

    QA Estimation:

    • Separate estimation for content testing (if content is final)

    • add time for QA after WP Rocket activation

    • proper BE testing

    Add a separate estimate for content testing  – content testing was not specified in the estimate, content was located in different folders (Artem Makarov)

    BE testing – test tha main BE QA scenarious: Add more text, bigger image, other type of file…

    PM PROCESSES

    1. Analyze design and agree with the client not-PP development if the design in not 100% PP (in email)

    If cliemt wants a perfect pixel, demand a perfect design where everything is taken into account) (Artem Makarov)

    PM PROCESSES

    1. Copy important discussions from Slack to tasks (comments)

    So the QA and other teammates know what was discussed and what solution used

    TEAM

    1. Use uploaded fonts + Git -> Delete merged branches

    Fonts shouldn’t be google fonts (PM)

    DEVELOPEMENT PROCESSES

    1. Content manager onboarding on early stage to help BE if there is too much content

    In general, a large amount of work with content instead of work with code (синяя звезда) .

     

    1. On the start call choose the functionality that can be started from BE stage

    Forms, load more, cookies sometimes should be developed on BE first to reduce double work.

    DEVELOPEMENT PROCESSES

    1. Analyze more the additional resources involving

    1. BE feedback – How necessary are two backs on such projects?

    2. QA feedback – convenient for me that there were 2 QA. This is a plus Also, there were no problems with two BE + But it was not very convenient to test at the beginning of the FE (Artem Makarov)

    TEAM

    1. Agree on the start call if the images for mobile should be uploaded separately

    images for mobile – PM and developers at the beginning of the project should agree where we need a separate field for mobile Img or video (Kate Hvozd)

    DEVELOPEMENT PROCESSES

    1. Forbid the image and video editing by developers

    Client should provide the final images and videos (Cropped and optimized).

    DEVELOPEMENT PROCESSES

    1. “/” in URL – remind on start call

    Discuss in the begining and make sure that all links have / at the end (in the content) (PM)

    DEVELOPEMENT PROCESSES

    1. If there is Span underline or animation with running line – discuss on start call the possible issues

    1. Span underline – if span class "underline" has a few words on mobile we had a bug with the underlining → solution → Add special rules for spans so it wraps fine. For animated links → solution → discuss with deigner that they should be always in 1 line with such animation. (PM)

    2. animation with running line – Be ready for the bugs when its not inline-block. → solution → Only inline-block element will have this animation 100% working correctly on all browsers. (PM)

    DEVELOPEMENT PROCESSES

    1. Word wrap rules discussion on start call

    word wrap – On the text pages we had "hyphens: auto;" but on other pages we have no wrapping. – Analyze the design and agree with dev team and client the wrapping rules and how we should act if we don’t have "hyphens: auto;" and the word doesn’t fit the container on mobile. Use correct lang for proper wrap

    DEVELOPEMENT PROCESSES

    1. Customizible position, background and z-index for all blocks by default.

     (Anna) – реквест на стартову тему

     DEVELOPEMENT PROCESSES

    1. SMTP and Recapture setup and QA

    Test a few times SMTP, especially on final stages. Ask client to not change the password without notifying us (PM). Always use client’s email.

    DEVELOPEMENT PROCESSES

    1. Discuss the launch in tiny detailes

    Second launch – took much unpredicted time. – details here – in 18 point. Reasons:

    • not much space on stage and live

    • due to the specifics of the changes, it was difficult to find the necessary files in the uploads folder

    Solution – Перенос частково вручну, частково через плагiн + щiльна робота з файлами через ssh

    Suggestion – Точно зафіксувати дату початку роботи на stage і переносити зображення починаючи з цієї дати:

    • врохувати це при створеннi архiву з зображеннями

    • aбо вказати в налаштуваннях плагiну WP DB Migrate

    https://gyazo.com/11a2cc957eb2a749a1f8a99361ee8571 

    DEVELOPEMENT PROCESSES

    1. Positive Jira prosses feedback

    I really liked the organization and priority of tasks in Jire. That there was a separate task for each role and that there was a general task with subtasks within it. It is also convenient that PM himself reassigns a specific task to QA when subtasks are done. As a result, there were not a lot of duplicating tasaks that were incomprehensible to me in the jira. (Artem Makarov)

    TEAM

    Next project:

    Project: OneLine: Migrol

    Team: PM: Kate Hvozd ; FE: Andrij Rehush ; BE: val.b (Unlicensed) ; QA: Artem Makarov ; Team Leads: Artem Gnibeda , Honcharuk Oleh Pavlo Trukhin

    Link to the Retrospective document – Retrospective

    Висновки

    Опис

    Відділ

    1. If there are a few emails in the row – each should be tested separately to make sure it was triggered by correct trigger (actition).

    Win email sent before winning. Solution – Rewrite the logic.

    (issue captured on the final tests, but developer said that it’s not easy to change the trigger, so we implemented some delay in email sending to cover this issue. However the client reported a bug anyway.)

    DEVELOPEMENT PROCESSES

    1. WP setup – Analyze the possible amount of fields and divide it accordinly to not exceed the limit or change the limit in advance.

    some WP fields dissapered from theme settings because limits were reached.

    Solution – Changed the limits in WP. (The issue apeared after we’ve implemented a few new fields).

    DEVELOPEMENT PROCESSES

    1. After each even small change the full functionality should be tested (even if it seems like the change is not connected to anything else. Including each email and their amaunt).

    Links don’t work, the page reloads on click + triggers a duplicate email sending.

    Solution – Links fixed, so they stopped trigerring the page reload and duplicate email sending.

    DEVELOPEMENT PROCESSES

    1. Set up correct receivers for emails that are triggered by crons. Be careful with transfers to prevent the code rewriting

    Duplicated Reminder emails (and after fix appeared again)

    Solution

    • 1.06 (before launch) – changed the logic so users receive personalized emails and are o in the copy of each other

    • 5.06 (after launch) – the fix made 1.06 was accidentally rewritten during some next transfer, so the fix was put back.

    DEVELOPEMENT PROCESSES

    1. Testing of the complicated functionality should include checkup of all the positive scenarios step by step. (To make sure that data saves correctely – accordingly to user actions)

    Prize limits were reaching too fast as “-1” was on applied to more prizes then needed.

    Solution: “-1” was applied to correct prize (not all the prizes form interests that were chosen)

    DEVELOPEMENT PROCESSES

    1. After form testing – always make sure that all the fields data appeared in WP and emails.

    Sometimes some fields do not appear in the WP table (but saved in DB)

    Solution:

    • the frst time it was reported there were a few such cases. We haven’t found the reason why it happened and were monitoring it.

    • then we assumed that the code should be rewritten but it will be too dangerous, so we’ve just moved the data from DB to the table and DB.

    DEVELOPEMENT PROCESSES

  • PM + Dev cooperation document

    (синяя звезда) Комунікація в команді

    • Уся команда має ставити реакції на повідомлення в загальних чатах і приватних повідомленнях, щоб позначити, що ви побачили повідомлення.

    (синяя звезда) – ставимо, коли побачили і прочитали повідомлення.

    (синяя звезда) , (синяя звезда) – ставимо, коли виконали те що описано.

    (синяя звезда) , (палец вверх) – так / згоден.

    (синяя звезда) , (палец вниз) – ні / не згоден.

    • Обговорення проектних питань мають відбуватися у каналі проекту, аби залучені члени команди були в курсі апдейтів.

    • Якщо обговорення задачі було довгий час назад (тиждень і більше) та по тому ж питанню є апдейти або нові прохання до розробника, РМ має створити нове повідомлення в каналі, щоб нові деталі не загубилися, до якого має бути доданий лінк на попередній тред.

    • Якщо РМ пише розробнику в особисті повідомлення стосовно задачі, то до повідомлення має бути прикріплений лінк на задачу.

    • Команда має бути відкритою до комунікації з РМ, та спілкування щодо задач має бути доведеним до кінця: коли задача або зроблена, або визначені подальші кроки стосовно вирішення питання.

    • Комунікація по проблемних питаннях проєкту чи питаннях по задачі повинна бути чіткою та зрозумілою, апдейти/репорти по задчах донесені структуровано, щоб РМ міг передати технічно зрозумілий фідбек клієнту.

    • Усі члени команди мають ставитися із розумінням пріоритетів, встановлених РМ. Поважаємо та розуміємо пріоритети, встановлені РМ.

    (синяя звезда) Апдейти по задачах

    • При передачі сторінки на Code Review, потрібно описати виконані дії та додати лінки до відповідних сторінок та merge request (в гілку stage) в задачу в Jira:
      FE — на фронтову сторінку,
      BE — на кінцеву сторінку на стейдж/прод.

    • Репорти по задачах мають бути оформлені чітко та лаконічно, з урахуванням пояснення причини виникнення проблеми та підібраного рішення, аби колегам було зрозуміло, що саме було виконано, а РМ міг передати зрозумілий клієнту апдейт/фідбек.

    • Формуючи репорт по задачах, розробник має вказувати, чому задача була виконана тим чи іншим чином. Наприклад, клієнт попросив виконати задачу якимось чином, попри те, що розробник пропонував інший підхід. У такому випадку, це треба зазначити у репорті окремим пунктом.

    Приклади апдейтів – Приклад 1, Приклад 2

    • При виконанні задачі необхідно змінювати статус завдання: якщо воно завершено розробником, то воно не залишається без дії, а переходить у статус "Ready for QA", змінюючи Assignee на QA.

    (синяя звезда) Труднощі з задачею

    • Якщо оцінка по задачі занижена, слід повідомити РМ про це завчасно.

    Коли є відчуття що не вкладаємось в есімейт, варто повідомити про це раніше, ніж вичерпається час, в який було оцінено, чи хоча б тоді, коли досягли верхньої межі естімейту.

    • Команда має відкрито спілкуватися з РМ та не соромитися звертатися до Тім-ліда у разі проблем із завданням.

    Послідовність дій при виникненні проблеми

    1. Розробник має провести ресерч по задачі/виявленій проблемі.

    2. У випадку, якщо рішення не знайдено самостійно, розробнику слід повідомити про проблему в загальному чаті, описати варіанти вирішення запиту та тегнути РМ і Тім-ліда.

    (синяя звезда) Робочі години та days-off

    • Уся команда повинна бути присутньою у робочий час та старатися відповідати на повідомлення швидко. У випадку, якщо зараз зайняті, слід коротко відписати на кшталт: “я зайнятий, зможу обговорити через …”

    • Якщо член команди не зможе працювати у певний проміжок часу, слід попередити Тім Ліда про це завчасно та додати часову рамку, коли зможе повернутися до роботи.
      В свою чергу, Тім Лід має передати цю інформацію у каналі РМО.

    • Слід трекати час на задачі у реальному часі через TimeDoctor, коли над ними працюємо. Повинно бути затрекано 8 годин за день.
      Якщо розробник не використовує трекінг в TD, то час має логуватись вручну до кінця робочого дня.

    • Коли йдемо на перерву чи обід, оновлюємо статус в Slack та вказуємо час, коли повернемося у текстовому полі.

    • Якщо потрібно взяти вихідний або відпустку, обовʼязково має бути створений відповідний запит в Hurma. Тоді колеги, що взаємодіють з даним розробником на різних проєктах, мають поставити позитивну/негативну реакцію на цей запит в Hurma (відповідно до того, наскільки сильно людина потрібна на проєкті саме в ці дати), а фінальне затвердження вихідного/відпустки проставляє РМО.

    • Коли беремо вихідний або відпустку, оновлюємо статус в Slack на (синяя звезда) vacation та вказуємо перший робочий день після відпустки у текстовому полі.

  • Access that we should get from the client

    Steps:

    1. PM asks the client: “What hosting do you plan to use? Is the DNS and hosting on 1 service or they are separate?”.

    2. PM asks the client to provide “access to the hosting panel” (or c-panel = “light access”).

    3. The client can provide access to the hosting panel or say that he can’t do it and give some other access, in both cases PM should send all the accesses he got from the client to Roman Kluiko (SysAdm/D.OPS) along with the answer on the question 1.

    4. SysAdm/D.OPS checks the access according to the instruction provided by Oleh Honcharuk (Tech lead) and gives positive feedback to PM if there is enough access for the development or negative feedback with a list of additional required accesses that PM should request from the client.

    5. SysAdm/D.OPS should add the live access that developers will need to the project passport along with some comments if needed, so the developer knows the specifics of some access if there are any specifics.

    Instruction for Roman Kluiko (SysAdm/D.OPS) will be added by Oleh Honcharuk (Tech lead) below:

    1.

    2.

  • Projects Incident Log

    Project

    Name of incident

    Date / Time

    Request from client

    Involved (Internal)

    Involved (External)

    Solution

    Conclusion how to avoid

    https://cheitgroup.atlassian.net/jira/software/c/projects/W4W/boards/120

    Long page loading and problem with the server

    21.06.2023

    https://onelinemarketing.slack.com/archives/CQWNJ94M6/p1687346297968709
    https://paste.pics/PSNWY

    Alex Lozitskyi
    Olga Gomon
    Slava Moisieiev
    Dima Sviridenko
    Oleh Honcharuk
    Ivan Atroshchenko

    Boris Schaefer
    Egzon Cekaj
    Chiara Gragnano

    Our steps:

    • Review server settings and configurations.

    • Check server logs for any anomalies or errors.

    • Assess server performance and identify any potential issues.

    • Examine the codebase for any errors or vulnerabilities.

    • Collaborate with the team to brainstorm possible explanations and solutions.

    Note: The same problem was a year ago due to the fact that they did not pay for hosting

    1. add dmitriy.sviridenko@cheitgroup.com as admin to the account (not owner) he also will be aware.

    2. pay for one year ahead 

    3. put once a year 20.06 notification in calendar to check the server billing.

    4. change owner to someone responsible for all servers/hosting/billings in company.

    Casinor

    NS name change was done 2 times and 301 redirects didn’t work for some time after launch that possibly lead to the rank drop.

    1.09.2023

    Hmm slightly confused here Kate as it seems there is non of the /go/urls pulled through into the new build?

    Rankings and traffic is going down rapidly. Something is very wrong

    Kate Hvozd

    Alex Lozitskyi

    Valeriy

    Igor Korobeychenko (SEO)

    Artem S (SEO)

    Anna Nikitina (SEO) 

    Dan, Mario

    Our steps:

    1. transferred 301 settings ASAP.

    2. Full SEO audit with Google search console checkup.

    3. Sending the client constant updates regarding our progress in searching the reasons.

    4. Sending the client reports with analisys.

    5. Checking the issue few days / weeks later

    Note: similar rank drops were on the website a few times before the launch, so we are not sure that our mistakes realy influnced the ranking much.

    1. After transfer check were the 301 settings tranferred

    2. If the 301 were not tranferred – make the export import from stage carefully as the stage 301 settings will have stage domain “hardcoded”.

    3. don’t change ns name more than 1 time during transfer.

    4. If the website is SEO sensitive always provide SEO audit immediatelly after launch.

    https://cheitgroup.atlassian.net/jira/software/c/projects/FGZ/boards/188

    Stage indexing

    18.09.2023

    Egzon tagged Alex in slack

    Anna Potiiuk
    Alex Lozitskyi
    Dima Nagaev
    Oleh Honcharuk

    Egzon Cekaj

    • Figured out the reason why – when checking Page Speed the developer switched off htaccess and after forgot to switch on again.

    • Checked all our stages to figure out if the same issue is reproducing.

    Note: the same problem appeared on several staging site after checking

    • Set the auto checking+closing each 15 min for all stages on our server

    • If stage is on external server need to pay attention to this (PM+Developer)

    Flytte

    The emails are not sent

    16.10.2023

    We have an URGENT issue for flyttesiden and flytteskjema.

    We have not received the emails with sign orders that should have been sent out 14th (Saturday)

    Andrii Kupriianov, Mykola Pashchuck, Oleh Honcharuk

    Mikael

    Our steps:

    • get access to the Google admin account (Workstation)

    • setup new emails in workstation

    • change SMTP settings

    –

    Chiidaspa

    The main page lost the styles

    31.10.2023

    the Chiida Spa site is down: https://prnt.sc/LdPIYNS31oAF
    Can you please check what the issue is and solve it?

    https://cheitgroup.slack.com/archives/C018CAMQQ8G/p1698765620549709

    Andrii Kupriianov
    Valeriy Boyko

    Danny Kurasinski

    Our steps:

    • Review cache settings

    • Activate plugin Autoptimize

    • Clear cache

    –

    Chiidaspa

    Don’t work checkout on last step

    02.11.2023

    Booking Issue URGENT

    Issue = https://prnt.sc/1-Njh6PANPT-
    Link = https://chiidaspa.ch/termin-buchen/  

    Andrii Kupriianov, Mykola Pashchuck

    Danny Kurasinski

    Our steps:

    • understand how booking is formed (on js)

    • disable js aggregation (because the order was collected on js)

    • update the plugin and three lines to it

    • write corrections in the template for the lines so that the form itself is not cached in any way

    –

    https://cheitgroup.atlassian.net/jira/software/c/projects/CC/boards/258

    Broken styles on the new pages

    14.03.2024

    After upload of a new page to the live site, styles of that page got broken Screenshot

    Daria Synenko Dmitriy Nagaev

    Sam

    Purge the server cache

    After pushing each new page to live site, the styles on that page break, so after uploading to live, you need to clear the server cache on Cloudways.

    https://cheitgroup.atlassian.net/jira/software/c/projects/FGZ/boards/188

    WP-automatical update

    10.04.2024

    https://cheitgroup.slack.com/archives/C04G9107NER/p1712731382108639

    https://prnt.sc/nJhONsmlPXak

    Dmitiriy Nagaev
    Pavel Trukhin

    Luca Manz

    1. Running a website test after the update

    2. Turn off automatic updating

    1. Raise a question about disabling automatic updates on Support projects.

    2. Discuss this with the client on further projects at the beginning

    Saclab

    Incident #1 [Users can’t check out]

    21.05.2024 1:49 pm

    please check urgentlh it seems that users can’t check out

    tested payment via Credit Card – failed. https://app.box.com/s/ko0a5y7s3jb2tk0tjvcigp77khuizazz
    Affected methods reported by customers: CC, paypal, eventually Apple pay. Mollie Order ID note in failed order: https://app.box.com/s/3zgxnpefrkfdcuclmxrcyvpqlis8ex5o

    Andrii Kupriianov Dima Savchenko (WP) Filipp Antonov

    Thư Phan Alexander Böhringer

    Deactivated and activated the Mollie plugin + updated the plugin.

    Update the payment plugins as soon as a new version is released

    Saclab

    Incident #2 [Critical WP error on the front]

    6.06.2024 3:52 pm

    [Urgent] Critical WP error for client who wanted to schedule a pickup


    SCLB-659

    Andrii Kupriianov Dima Savchenko (WP)

    Thư Phan Alexander Böhringer

    update the cache

    Purge the cache after update production

    OneLine: Migrol

    Incident #1 [Win email sent before winning]

    30.05.2024 9:26 AM

    (on live before launch)

    “fyi: I don’t know if I should already start doing bugherd tasks, since you are also still testing, but I got the instant win email before I spun the wheel. The e-mail should be sent when I am on the instant prize page.”

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    Rewrite the logic.

    (PM captured this issue on the final tests, but developer said that it’s not easy to change the trigger, so we implemented some delay in email sending to cover this issue. However the client reported a bug anyway.)

    If there are a few emails in the row – each should be tested separately to make sure it was trigerred by correct trigger (actition).

    OneLine: Migrol

    Incident #2 [some WP fields dissapered from theme settings because limits were reached]

    31.05.2024 8:44AM

    (on live before launch)

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    Changed the limits in WP. (The issue apeared after we’ve implemented a few new fields).

    Analyze the possible amount of fields and divide it accordinly to not exceed the limit or change the limit in advance.

    OneLine: Migrol

    Incident #3 [Links don’t work, the page reload on click – trigges a duplicate email sending]

    3.06.2024 10:02 AM

    (on live before launch)

    •  IMPORTANT: ALL Links of the Prices don’t work. This Link here doesn’t work: https://prnt.sc/sU8p3Z5jI5JE It gets me over here

    • Client called, they said they received 2 confirmation E-Mails when they won 5Rp, Mobility. Could you maybe check, I will as well

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    Links fixed, so they stopped trigerring the page reload and duplicate email sending.

    After each even small change the full functionality should be tested (even if it seems like the change is not connected to anything else. Including each email and their amaunt).

    OneLine: Migrol

    Incident #4 duplicated Reminder emails (and after fix appeared again)]

    1.06 and 5.06

    (on live before and after launch)

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    • 1.06 (before launch) – changed the logic so users receive personalized emails and are o in the copy of each other

    • 5.06 (after launch) – the fix made 1.06 was accidentally rewritten during some next transfer, so the fix was put back.

    • Set up correct receivers for emails that are triggered by crons.

    • Be careful with transfers to prevent the code rewriting

    OneLine: Migrol

    Incident #5 [Prize limits were reaching too fast as “-1” was on applied to more prizes then needed]

    4.06.2024 4:37PM

    (on live after launch)

     Car Wash for exmaple was won like more that 500 times today. In the backend I see this: https://prnt.sc/N5xSGxyHIAl_ and thats all of them.

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    “-1” was applied to correct prize (not all the prizes form interests that were chosen)

    Testing of the complicated functionality should include checkup of all the positive scenarios step by step. (To make sure that data saves correctely – accordingly to user actions)

    OneLine: Migrol

    Incident #6 [Sometimes some fields do not appear in the WP table (but saved in DB)

    3.06 , 10.06.2024

    (on live before and after launch)

    3.06 – Question, all of the fields in the form are mandatory. But why was this data transferred from him to the backend? https://prnt.sc/ujBXgA1EzgVg 

    10.06 –  I pulled out the lead list and in which ones the first or last name is missing.These are mandatory fields for us. Do you know why they are empty? https://prnt.sc/7haPj4nuYF7j

    Kate Hvozd val.b (Deactivated)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    @Amire Berisha 

    • the first time it was reported there were a few such cases. We haven’t found the reason why it happened and were monitoring it.

    • then we assumed that the code should be rewritten but it will be too dangerous, so we’ve just moved the data from DB to the table and DB.

    After form testing – always make sure that all the fields data appeared in WP and emails.

    Flytteskjema

    Incident № 3. The emails are not sent

    14.06.2024

    We have an URGENT issue again

    The sign orders (on email) stopped working once again….. We did not receive them for Flytteskjema

    Andrii Kupriianov Dima Savchenko (WP)

    Mikael Petrowski

    Our steps:

    • access to errors log on Flytteskjema server

    • back to simple SMTP settings

    The reason is the blocked email post@flytteskjema.no

    need to investigate the reason of blocking and find the approach to avoid

    One-Line: One-Line (support)

    Broken animations around the website

    12/07/2024 16:08 – 16:38

    URGENT: on the whole website the animations are bugging and sometimes the user is not even able to scroll
    Example: Screen Recording 2024-07-12 at 3.07.01 PM.mp4 Please fix asap, this can’t happen.

    Anna Lukyan
    Artem Gnibeda (Deactivated)

    Illia Bilyk (Unlicensed)

    Oliver Gehrig

    Artem Gnibeda (Deactivated) reverted the changes implemented the day before (core dev and team lead were off that day)

    1. Dev – test their changes, even though QA will test them later

    2. QA – read comments more carefully

    3. QA – even without additional comments, review the entire website after implementing those tasks where changes can affect more than just one page

    4. PM – review the site after such changes as well

    5. Dev – avoid manual deployments

    Saclab

    Incident #3 [Website is down for 2 hours]

    20.08.2024 2:50 pm

    could you check if the website is down? thanks

    Andrii Kupriianov Dima Savchenko (WP) Roman Kliuiko

    Thư Phan

    Possible solutions:

    1. Upgrade server plan, but let’s check several days the loading

    2. Use security level in cloudflare during possible next downtime

    Need more info, monitoring

    Saclab

    Incident #4 [Website has been down several times]

    15.10.2024 11:49 am (Kyiv time)

    the website was down again and some times was super slow for a brief moment. Could you please take a look and give me an update? thank you

    Andrii Kupriianov Dima Savchenko (WP) Roman Kliuiko

    Thư Phan

    Solution: Upgraded server plan

    Need more info, monitoring

    Saclab

    Incident #5 [Website has been down]

    20.10.2024 3:38 pm (Kyiv time)

    Website down

    Dima Savchenko (WP)

    Oliver

    Solution: added new rule to the Confluence about user agent that attacked the website by link utm_source=google&utm_medium=sea&utm_campaign=fr_pmax_nbr_bags&gad_source=1&gclid=EAIaIQobChMI573P7rqciQMV9VcPAh3-ajmhEAQYByABEgJOZfD_BwE

    Monitor new attacks and add new rules to the Confluence

    Win4Win

    Two step form is not working

    27.11.2024
    9:07 AM (Lisbon Time)

    The form in french from tcs https://win4win.ch/fr/concours/concours-tcs/ is not working again, you can click on the first step button and nothing happend

    alex.l@cheitgroup.com Anna Potiiuk Anna Aksonenko Pavlo Trukhin (Deactivated) Honcharuk Oleh

    Chiara, Egzon, Labi

    We are using here nonсes (for adding more security to cut off spam).
    Before we excluded the nonces from caching, but they are still cached by the litespeed plugin, so the security check does not work.
    Solution: The dev wrote all the nonces in the plugin in a more explicit way. According to the plugin documentation, it should work, but plugins sometimes just glitch, we cannot influence it on our part

    Keep monitoring the form

    Win4Win

    Annoying recaptcha

    27.11.2024
    9:07 AM (Lisbon Time)

    https://win4win.ch/fr/concours/concours-tcs/ – the rechaptcha is appearing, we whant to have this in the background

    Anna Aksonenko

    Chiara

    Solution: reset recaptcha.
    Here https://www.google.com/u/2/recaptcha/admin/site/713805202/settings
    https://prnt.sc/mRUM1yVlFZ_s the Easiest for the users should be set

    Specify with the client in advance before he creates the recaptcha, so he could set the Security level in settings.

    Win4Win

    Reminders sent a lot of times

    26.11.2024
    4:20 PM (Lisbon Time)

    Some clients are complaining to receive the reminders 40 times. An other one said like 80 times. This one said even 150 times: https://media.one-line.ch/YPpmwivx

    alex.l@cheitgroup.com Anna Aksonenko Honcharuk Oleh Pavlo Trukhin (Deactivated)

    Chiara, Egzon, Labi

    Solution:

    • We have added a code that will prevent several crones from running in parallel, i.e. if one is already running, it will fully process the list, mark it processed, and only then the next crones will start and it will not get emails from the first crones again

    • We also expanded the logs with a more accurate time mark and response status from Sendgrid. This is not directly related to resolving the problem, but it will provide more accurate information.

    Test such user cases more, simulating a large number of simultaneous registrations.

    OneLine: Play2win

    Incident #1 [48h reminders stopped sending on competitions]

    28.11.2024 3:35PM

    (on live after launch)

    client didn’t know about the issue (after win4win recent reminders bug we decided to fix Play2win bug quietly and track time to another task.)

    Kate Hvozd

    Anna Aksonenko (fixed)

    Artur Bulan (main dev but was on the sick leave)

    Artem Makarov

    Pavlo Trukhin (Deactivated)

    nobody

    Request optimization: some checkups moved from code to DB request directly, so the data we receive became smaller and more actual.

    Reason the issue appeared:

    Request didn’t include strict timeframe (we were taking all old registrations created earlier than some date and later it lead to the accumulation) and in the code the registrations without partner ID were excluded (but they were not excluded from the request, so we received 1000+ rows, а потім у коді крутили їх виключаючи по одному).

    If it’s a new code – the Code review was required and possibly there the logic problem could be captured.

    Reminder log should be checked from time to time or additionally some monitoring with Slack notification applied. If the log was checked from time to time it should be possible to notice the gradual increase in reminders number.

    (This issue couldn’t be captured by the one time testing)

    Dan Aufhttps://cheitgroup.atlassian.net/jira/software/c/projects/HN/boards/124richtig: CasinoBonusDeals

    Home page infinite redirect (other pages worked)

    14.03.2025

    Website is down

    Roman Kliuiko

    Honcharuk Oleh Eugene Rudyk

    Dennis

    Dan

    Mario

    https://jmp.sh/k8j6QCcT

    (Custom SSL/TLS)
    Changed the encryption mode that Cloudflare uses to connect to origin server.
    From “Flexible” to “Full (Strict)”

    task in Jira with full comment

    It’s recommended to check the live site before making changes on the stage. If possible, review installed plugins that might affect the live site, even if they are only on the stage, as there was a suspicion this could have caused the issue.

    https://cheitgroup.atlassian.net/jira/software/c/projects/HN/boards/124

    All data from the files has disappeared on the country pages.


    HN-371

    25.09.2025

    https://prnt.sc/za6IDY_rq9X4
    Передавайте привіт розробнику. Без піздєца він не може. В сторінках країн зникли всі дані, які тягнулись з файлів.

    Eugene Rudyk
    Honcharuk Oleh

    Client (Yehor Velychkovskyi)

    Fixed the issue (was caused by the task that has beed implemented before –


    HN-366

    )

    Що пропонуємо:

    • Протягом наступних 2 місяців на всі завдання, де є функціональні зміни в коді (не стилістичні правки на кшталт розмірів шрифтів тощо), ми будемо залучати QA.

    • QA перевірятиме не лише конкретну змінену таску, а й проходитиметься по основному функціоналу сайту.

    • За цю додаткову роботу ми не будемо виставляти інвойс.

    • Для якісного покриття нам буде потрібен від вас список ключових критично важливих сторінок/функціоналу, на які слід звертати особливу увагу під час перевірок.

  • Workshop Links

    Manuals for software

    Project Management

    BA

    Recordings

    Part1
    Part2

    SEO

    Development

  • Incident #1 [Name of Incident]

    Name of incident

    Date / Time

    Request from client

    (link to the chat in Slack, copy-paste, screenshot)

    Involved (Internal)

    (list all team members / involved people from CheIT side)

    Involved (External)

    (list all stakeholders from Client’s side)

    Solution

    (how the issue was solved – tech steps from Dev)

    Conclusion how to avoid

    (comment how we can avoid such situation in the future)

  • [Project Name] Incident Log files

  • Weekly Reporting Template

    Please send this report to the following list of recipients: pm@cheitgroup.com by 11-00 on Monday

    Project Schedule & Scope Status

    Scope/Projects

    Status

    Deadline

    Budget

    Additional Requests

    Team

    Update

    Estimated

    Spent

    Estimated

    Spent

    Project 1 

    ON TRACK

    10.11.23

    100h

    50h

    10h

    –

    Project 2 – Milestone 1

    WITH RISK

    Project 2 – Milestone 2

    PAUSED

  • Involving Team-leads (Project process)

    (синяя звезда) Estimation phase

    • PMs, devs should read the incoming documentation very carefully. Developers need to understand all inputs.
      PMs should understand and highlight what they think are important points (step-by-step forms, integration, personal account) – add this points as a comment to involve Team-lead (internal estimation)

    • In the case that some functionality is not clear, raises doubts or risks, the developer MUST inform the Project Manager about it. After that, the PM organizes a call with the Team leader and the developer

    • Approval of a detailed estimate must always be confirmed by Team-lead

    (синяя звезда) Pre-development phase

    • Team leaders MUST be involved in the first kick-off call

    • Team-lead MUST create environment (Git / stage) for the project

    • Team leaders are involved in the project for consultation when the functional work will begin, which causes risks or difficulty of implementation

    Create a task for some sprint or in backlog right away on the team leader so that we don’t forget to include it.

    • When changing the tech-requirements on the project, PM MUST to notify the Team-lead immediately

    (синяя звезда) Development phase

    • Team-lead MUST be involved to the Code Review (by pages / particular parts of the scope)

    • PM should gather a list of all plugins and components for the project and send it to Team-lead for approve

    • Team-lead should participate in Daily meetings (ONLY in case some functionality scope is discussed or tech issues appear)

    (синяя звезда) Go-live phase

    • Before Go-live Team-lead should receive from PM all access details needed for transfer:
      – Domain control panel (if it needs to be parked on another hosting)
      – Production server
      – Hosting control panel
      – SSH\SFTP\FTP
      – Database
      – Access to product services (ex. Hubspot, Mail Chimp)
      Team-lead MUST check all accesses and let PM know if something is missed or not working

    • Team leader MUST be involved in going-live process

  • Jira | Project creation

    1. Go to Jira Projects https://cheitgroup.atlassian.net/jira/projects and click “Create project“ button

    2. In Project templates pick “Software development“ and pick the needed template – “Kanban“ / “Scrum“ – WE MOSTLY USE “Kanban”

    3. Click “Use template“ button

    4. Choose “Company-managed project“

    5. Enter project’s name (it should be in the format Client Name: Project Name), and click “Create project“

    Good job – Project created (синяя звезда) Now we need to set up configurations:

    6. Go to Project Settings (left menu)

    7. Change Project Lead: Details → Project Lead (to PM who requested project creation)

    8. In Projects Settings, Click “People” and add PM who requested the project creation with roles “Administrator“ + “PM”, also add Sophia Bilyk as “Administrator“

    9. In Projects Settings, Click “Workflows” → “Add Workflow“ → “Add existing“

    • For Scrum projects, pick “Standard Workflow Scheme (version I)”

    • For Kanban WP projects, pick “Standard Workflow Scheme (version with backlog)”

    • For Kanban Webflow projects, pick “Webflow Workflow Scheme”

    • For Support projects, pick “Standard Support Worklow“

    → Click “Next“ and tick all checkboxes → Finish

    → Click “Publish“ → “Associate“

    1. In Projects Settings, Go to Work items → Types → Actions → Edit work types

      Знімок екрана 2025-09-12 о 15.30.08.png

    → From Available Issue Types (right column) drag & drop following Issue Types to the left column: Internal, CR, CB, Freelance

    Знімок екрана 2025-09-12 о 15.32.02.png

    -> Click “Save“

    – Additionally, if you need to add someone to the project:

    1. Go to Jira Projects https://cheitgroup.atlassian.net/jira/projects, find the specific project

    2. Click three dots → Project Settings

    3. Click “People” and add person with specific role

    Assigned Project Manager next steps

    1. Go to your project → “active sprints” → 3dots → “configure board”

    1. Click on “columns“

    1. Your board will look like this

    1. Create new columns and assign each ticket from the left to the particular status. So the new board should look like this

    1. Finally, Drag and drop “To-do“ status into the left column

    Congratulations. Everything has been setted up (палец вверх)