Sprint Retrospective - by.U by NAZWA GHEFIRA

nazwaghee — 2025-07-07 01:34:06 UTC

Dalam mengikut sprint Retrospective, peserta diharapkan untuk:

menuliskan feedback dari hal hal yang sudah dilalui selama mengerjakan sprint sebelumnya
terdapat 3 kolom yang dapat diisi oleh peserta yaitu, Start, Stop dan Continue.
Start -> Apa apa saja yang diharapkan oleh peserta untuk dapat diimplementasikan di sprint selanjutnya.
example: start listen technical concerns from developer
Stop -> Apa saja yang hal hal harus diberhentikan sebelum memulai sprint baru.
example: Stop melakukan deployment secara dadakan
Continue -> Apa saja yang sudah dilakukan pada sprint selanjutnya dan diharapkan untuk dilanjutkan di sprint berikutnya.
example: Sharing knowledge

Test Case not created yet in Jira On Prem, even already passed in Excel Sheet

2025-07-07 04:13:13 UTC

So we need to work 2x times, pass first on excel, evidence later

2025-07-07 04:18:24 UTC

please attach ss of figma into jira epic with the scenario, so it will help QA can easier to create testcase:))

Shifting in the afternoon work onsite

2025-07-07 04:21:20 UTC

I live quite far from Jakarta, and it takes me approximately 2 hours to commute. With an afternoon shift, I went home until around midnight, which could potentially affect my health. I hope we can work from home for afternoon shifts.

jadwal libur

youdonthavetoknowmyname24 — 2025-07-07 04:22:17 UTC

kalo bisa, libur nya tuh 2 hari berturut - turut JANGAN SELANG SELING. misal: minggu ini dapat jadwal libur di hari senin dan jumat. harusnya alokasikan senin-selasa aja atau jumat-sabtu sekaligus. kalau selang-seling kurang efektif istirahatnya. harapannya biar bisa lebih produktif kerjanya.

Overtime

2025-07-07 04:30:11 UTC

What about those of us who worked overtime last week from 9 AM to 10 PM at TSO without any support from Phincon? Even though there’s no overtime pay or compensatory leave, could Phincon at least provide meal allowances? In my opinion, this is inhumane — we worked like this for four consecutive days without receiving any benefits at all from Phincon.

Assignment

2025-07-07 04:38:19 UTC

Assignment ready before 10 AM please

2025-07-07 04:44:34 UTC

stop working on weekend and outside of working hours. you not robot.

WFH

2025-07-07 04:44:53 UTC

WFH

2025-07-07 06:19:12 UTC

2025-07-07 06:21:31 UTC

WFH

2025-07-07 06:21:43 UTC

Test Case Steps and Expected Results sometimes are confusing

2025-07-07 06:24:26 UTC

Many copy paste steps and expected results are being written. This makes the QA confused and have to ask multiple times what is the proper steps for a feature and whats the expected. This could lead to miscommunication of the feature if the steps and expectation are not written properly

WFH LAH MASA ENGGA?

2025-07-07 06:25:22 UTC

2025-07-07 06:35:39 UTC

WFH

WFH tp rolling orang"nya yg wfo

2025-07-07 06:35:44 UTC

Tulisakan sesuatu yang indah

2025-07-07 06:38:23 UTC

Please also pay attention to the number of TCs assigned, not just the SCA assigned. Each SCA has a different number of TCs, and it is requested to be run on that day.

What if each QA at that time was assigned a large number of TCs, many TCs that could be run but could not be done because of limited working hours (additional SCA at the end of the hour)?

Do TCs also have to be run until all 'Not Started' runs?

2025-07-07 06:50:21 UTC

One of the challenges is communication and background. It is quite difficult to communicate our challenges, where PMs also have difficulty understanding the technical POV that usually occurs in testing. And also limited by language.

wfh

2025-07-07 06:59:52 UTC

2025-07-07 07:31:02 UTC

VPN connection and internet connection

2025-07-07 11:45:10 UTC

There is instability for VPN connection and internet connection. When testing using OPX and the web, it's always a VPN shutdown. When using a stable VPN, the internet is so slow, and I get a 404 when testing.

Connecting and reconnecting take many times.