3 ms·

If you don't mind elaborating i'm curious about this workflow / perspective. 1. What are the daily updates/planning providing to other team members / managemen

If you don't mind elaborating i'm curious about this workflow / perspective. 1. What are the daily updates/planning providing to other team members / management? Are they stored like a git log somewhere for people to reference? 2. If you use a ticket queue/system would this seem redundant as your boss could just look at the queue, ticket comments, git commits, etc? 3. Do you have a project you support regularly or if a new project comes online how would management relate your update to the progress of the project? 4. Does the industry you work in have some strict bounds that you can pre-determine what you are going to do day-by-day? Otherwise what purpose do the daily updates + the write up on your plan for the next day serve? 5. If you have an issue that spans multiple days are you just giving a high-level overview or something else?

john_the_writer 4y ago
1. yes.. They are stored and can be read by any team member. They sort of replace the standup. I can (and do) look at what others are planning for the day. Sometimes I ask to jump in and pair. 2. My direct boss can look at this (ticket/git), but his boss cannot, because he's not tech, so looking at git commit isn't helpful. 3. I work on a pile of projects, which is part of why the update works. Not all my tickets are on the same board. - the progress on projects is based on the tickets in those projects. This email/journal is not an indication of progress. 4. Nope (no industry bounds). I'm mostly just guessing at what I'll be doing for the day. Sometimes I don't do anything I planned, because something came up, or I have a sucky day and get blocked. 4.1 What's the use? I can see what others are planning and sometimes I can pair, or even ask them to hold off, because I'm working in that area. Oh... I'm an Elixir dev, so I can also telegraph what API features I'm building to the JavaScript team. 5. It's all just a high level overview. It's sort of like an offline daily standup.

john_the_writer 4y ago

1. yes.. They are stored and can be read by any team member. They sort of replace the standup. I can (and do) look at what others are planning for the day. Sometimes I ask to jump in and pair. 2. My direct boss can look at this (ticket/git), but his boss cannot, because he's not tech, so looking at git commit isn't helpful. 3. I work on a pile of projects, which is part of why the update works. Not all my tickets are on the same board. - the progress on projects is based on the tickets in those projects. This email/journal is not an indication of progress. 4. Nope (no industry bounds). I'm mostly just guessing at what I'll be doing for the day. Sometimes I don't do anything I planned, because something came up, or I have a sucky day and get blocked. 4.1 What's the use? I can see what others are planning and sometimes I can pair, or even ask them to hold off, because I'm working in that area. Oh... I'm an Elixir dev, so I can also telegraph what API features I'm building to the JavaScript team. 5. It's all just a high level overview. It's sort of like an offline daily standup.