5 ms·
I much prefer stand-downs (I’m claiming the name now). At the end of the day, you tell your team what you accomplished for the day in an email. Everyone alread
by alexmingoia 6y ago
I much prefer stand-downs (I’m claiming the name now).
At the end of the day, you tell your team what you accomplished for the day in an email. Everyone already knows what they’re working on next because that’s part of the ticketing and schedule system your company uses, and decided at the beginning of the release period. If you’re blocked you go tell the person whose blocking you, or your manager.
When everyone wakes up and goes to work they can just get to work.
- xwdv 6y agoI like that better. It’s a pain in the ass waking up and not knowing what’s really gonna happen for the day until your standup meeting.
- paulmooreparks 6y agoThis. I really like this about Kanban. All of the work was already on the board. The to-do column was kept populated with tasks to be done, and there's complete visibility of what's in progress. As the lead I could look at the aging of each ticket and speak directly to the assignee about any issues. If we needed an ad-hoc meeting to deal with blockers we could do so, and invite the people needed. We'd have at least weekly meetings with the entire team and as many ad-hoc meetings as necessary, but no more.
- srtjstjsj 6y agoWhat if one day your head is in a different space? You have to call out sick until you are ready for one specific task?
- alexmingoia 6y agoIf one day your head is in a different space and you don’t feel like working, you suck it up and work anyway because you’re a professional. If you didn’t accomplish anything for the day, you put that in your end of day email/report and explain why, and what you need to do to ensure it doesn’t happen again. If you’re actually sick or need a day off you notify your superior. They will work with the team to pause or reassign your work while you’re gone, and when you get back you resume your work.