4 ms·
To echo pg on this- another trick that i was taught early on was to book out a day or half day per week for meetings. Slot them in, try and get people to come t
by imajes 17y ago
To echo pg on this- another trick that i was taught early on was to book out a day or half day per week for meetings. Slot them in, try and get people to come to you (helps if you have membership to a club or some such :)) and then keep people to their time slots. If they need to follow up - email or reschedule based on an action point.
One other point: agile standups seem to work well even for makers because they're bound tightly to the start of working sessions and last for a short time. They enable everyone to feel connected to each other on a team, but allow them to disappear back into their office or cube to work for the rest of the day.
- troels 17y ago> agile standups seem to work well even for makers because they're bound tightly to the start of working sessions and last for a short time. I think there's another thing going on too. Most meetings that developers go to have some specific purpose of importance. They are tactical, so as a developer you need to prepare (mentally and/or more concretely) for them. Standups - being recurring events - don't have this aspect to them. This makes them much less stressful.
- Periodic 17y agoThe problem with the meetings PG is talking about is they tend to be in the middle of productive blocks and they are long. The idea of an Agile standup is usually it is right at the start of the day, when people are still drinking their coffee and waking up, and they are short (the standing is deliberately to keep it short and to the point). Sure, you might have a 10 minute standup at the start of the day, but that's only 10 minutes off the beginning of your 3-hour productive chunk. They can also help you get into the flow by getting you thinking about work.