Never have been, never will be. We keep trying to solve them with technology, but they aren’t. The problem with meetings is that we all have different expectations of what they should and should not be, who should be invited, when they should begin, what their value is, and what should happen before and/or after them to make them a success and whether they should be on a recurring basis or not. But we don’t…
It is easy to organize something for ourselves. We know ourselves inside and out and can respond to simple changes without even thinking about it. It’s akin to being a passenger on a bumpy road where the driver is swerving to avoid the bumps and potholes – they know what’s coming, they are processing actions and ready for them. But you’re not and you’re dealing with them as they come. Your team is the passenger…
What will give your team the biggest impact today? What will make the biggest difference to what they are working on today? What will result in fewer calls coming into your support queue today? What will save developers the most time in building code? What will change how you do things? Focus on that, we all need something big to show progress against.
The smallest fix is the most critical release you will make to your software. It is the most critical because it is the most overlooked. “I ran it on my machine.” “It’s just this one isolated thing.” “It won’t affect anyone.” “We don’t have to tell anyone we’re deploying it.” Because it’s small we decide (for some odd reason) to treat it differently than our most significant releases and as such when something goes wrong,…
Yes. Or maybe it’s an area and not a room. We’ve been pretty flexible over the last few years where we met and got together and now we need to get back to doing that again when we are all together once more or when some of us are and some of us aren’t. The key to remember, which was always the problem before we went remote, was to ensure that everyone on board is…