Transparency
Developers must make their work transparent. The best way to accomplish this is to make our KANBAN board a fresh and accurate depiction of their work.
The ideal KANBAN board is one where small tickets move fast.
Small, fast
Developers must not let their assigned tickets lie still for too long.
More specifically, they must make any diversion from development visible on KANBAN.
If you find yourselves up against an unforseen obstacle:
- make a GitLab ticket for it
- assign it to yourself
- assign it a weight
- attach it to the milestone (if any) of your current ticket
- mark it as blocking your current ticket
- label the new ticket
state::ongoing - label your current ticket
state::blocked
If you know your work is being derailed, then make a ticket for the diversion as soon as it happens. If you are not sure, then stick with your current ticket and see how it goes. As a rule of thumb, if you find yourself working on it for more than 3 days, it is a good time to let the rest know what specific thing you are up against.
Merge Requests
A good MR is a narrowly focused MR. When splitting tickets, give the newly created ticket its own MR(s).