TG Bugs Continuous improvement by Arnold Roa

Not knowing what is our performance, how much a bug take to complete, what is our capacity

manolet — 2021-01-22 13:22:11 UTC

add a column with resolution date, manually set on last step and register it with weekly basis

[Documentation] Some bugs are not informative enough, make it harder to understand for devs, takes more time to reproduce. And is hard to resolve bugs faster.

manolet — 2021-01-22 13:23:39 UTC

* More descriptive reproduction steps.
* talk with all the CS team.
* VIdeo on LOOM with voice/
* QA check some bugs prior devs reproducing, enriching information, clearing out doubts, etc
* Meeting ( 9:15 )
* QA could anticipate what test will cover.
* Evaluate documentation platform. -> I will record a video with alternatives (this week).

Why?
* We dont always understand how feature should work?

Overwhelmed - Too many bugs, always in rush, increasing amount of bugs without resolution, Rushing leads to wrong quality, bugs.

manolet — 2021-01-22 13:24:46 UTC

Bring new dev.
Ask Jeff
Move temporary All dev team

[Clarity] The process is complex and doesn't bring clarity

manolet — 2021-01-22 13:25:57 UTC

[Priorization] It's hard knowing what to work on, too much tasks, too many critical priorities.

manolet — 2021-01-22 13:28:31 UTC

[Process] Hard to know if bug is being worked on, gathering information, stucked, etc

manolet — 2021-01-22 13:29:11 UTC

[Process and clarity] We dont know when QA step into, if we hotfix smthing but still working on the root cause

manolet — 2021-01-22 16:12:48 UTC

Related / duplicated items process

manolet — 2021-01-22 16:33:13 UTC

items are handled in multiple bugs and is hard to track.

Duplicated tickets makes risk of do work twice by different people and adds noise. We dont have a way to handle duplicated issues

manolet — 2021-01-27 09:44:14 UTC

Bundles case. We create a DEV parent task and log all issues there as subtasks. Both CS bug and DEV bug have to be referenced

[Flow] Lack of capacity, consistent hours and time spent working on bugs

manolet — 2021-01-28 15:15:49 UTC

Bugs are stuck on fixed improperly and Notify Client

manolet — 2021-02-04 15:23:56 UTC

Why we are rushing to fix loads of things but when we fix them, issues stay in this list for days? We maybe are investing our effort in things that are not the priority? I would expect that if we work in the right, critical think this list will be empty super fast.

We don't know what kind of solution we applied

manolet — 2021-02-04 15:24:24 UTC

fixed the root cause, patch, fix to data.

Not knowing what is being deployed

manolet — 2021-02-04 16:16:18 UTC

The unsorted list is too big, hard to know focus

manolet — 2021-02-10 09:53:33 UTC

Huge Unsorted list splited into Customer Detected and Detected -> Give us clarity on what should be attended first (customer reported)

Messages on teams are just an URL with no context

manolet — 2021-02-10 09:54:15 UTC

Template to talk about issues on Ms TEAMS. Developers now will include PR, explain what was the issue and how it was solved.

Title
Ticket URL
PR* (in case job is finished)
Summary of update

This allows us to understand all the context instead of just an URL without any information

Not clear what is in progress and developers switching focus frecuently

manolet — 2021-02-10 09:55:09 UTC

Added a In progress section, with limit of 2 per person. When developers start working on a ticket they must move to this section.
- Increase focus
- Give clarity on whats being worked on
➡ to mark next tasks to work on. Maximum 4 in the whole board

Not able to filter customers easily

manolet — 2021-02-10 09:55:50 UTC

Add a column for client and remove from title

Fixed improperly is forgotten, Tickets are left there for days

manolet — 2021-02-10 09:56:13 UTC

* Add to priority schema,
* communicate to everybody
* Yassen has reported how many are assigned to each person daily

Why this happen?
Lack of Documentation. Guessing.
Our current rate is 20%~

PROD Bugs are left behind

manolet — 2021-02-11 17:10:19 UTC

[Testing, QA] We are skipping merging into stage, which causes not automated tests run

manolet — 2021-02-25 13:04:47 UTC

[QA, Testing] We do not run test automatically on PR and we don't know results

manolet — 2021-02-25 13:05:21 UTC

* Jenkin box will test.

🔶 Our Fixed improperly (bounces) rate is high

manolet — 2021-02-25 13:06:08 UTC

Customers lose faith in the product

manolet — 2021-02-25 13:06:14 UTC

[Prioritization, speed] Slow updates, bugs takes longer than expected, not as prompty as it could be

manolet — 2021-02-25 13:07:00 UTC

Lack of functionality understanding [Documentation[

manolet — 2021-02-25 13:07:24 UTC

Often times there is a lack of intended functionality of existing features. How should it be working? How was it developed? Is it working correctly? Was it a miss when originally developed? All lead to difficulty in fixes.

Deploys - Stressful - high risk - didnt follow schedule, posponed, failed

manolet — 2021-02-25 13:07:43 UTC

[Metrics] We don't know our full capacity + focus factor, reducing the capacity to estimate how much we can improve by limiting the work in progress + increasing focus.

manolet — 2021-02-26 10:45:16 UTC

Dropping URL without context

manolet — 2021-03-04 16:23:38 UTC

not enought information