3 ms·
At my small company with 4 developers we post YTB: yesterday, today, blockers. It goes into a special slack channel and we all try to take the time to read othe
by ok_dad 5y ago
At my small company with 4 developers we post YTB: yesterday, today, blockers. It goes into a special slack channel and we all try to take the time to read other’s updates to help with blockers and stuff. Just a small sentence for each section. It’s works nicely but we also are super small. I prefer it to spending a 15 or more minutes on a video call listening to two people talk while everyone else ignores them. If we need to chat on video we self organize.
- nivertech 5y agoWhat's the point? If you closed/updated a ticket the interested party will see it, or you can explicitly mention them in the ticket. If you're blocked, you usually know who's blocking you, so you can contact them directly. Let's say you're a FE dev waiting for a BE dev to finish a specific API request for you. You ask him how long it will take, and if it's possible to provide a dummy API in the meantime. Alternatively you can mock this API by yourself. If no solution found you can switch to another task or escalate it to the PM. But this problem shouldn't exist in the first place. It's only exists b/c of Scrum. In mini-waterfall based SDLC methodologies (i.e. Design/Plan->Build(Iterate)->Ship cycles) developers are working on much larger work chunks (i.e. mini-projects), they're opening and managing tickets by themselves, instead of being assigned tickets opened by PM/PO. So if they're blocked on a specific API request, they still have other things to work on.
- ok_dad 5y agoI don’t know I’m not a frigging manager or pm. I just code for money and don’t complain constantly.