Teams don’t just work and they don’t just magically come together. It takes work and time. As soon as I see an email that ends with “let’s do this as a team” – I know there is something wrong, that the bridge isn’t there and this is a half-hearted attempt to deal with the problem. Building bridges between teams is not easy but if you’re writing your team announcements or motivation quotes in an email.…
I watched this clip twice tonight, only because it is so relatable. Do we know the problem we are trying to solve? Does everyone at the table understand what we are trying to do? Are we all on the same page? We can all nod our heads and go yes, but in that case, who are you helping. Understand the problem, get everyone on the same page, move forward.
I don’t worry about the falls. I don’t worry about the slipups. I don’t worry about things that are missed. Because we’ll figure it out, we’ll learn how to get better, we’ll figure out what we did wrong and fix the problem. The recovery is what I look for, if you can bounce back from defeat, from failure, from mistakes – that’s what will always matter. Will you blame your team? Will you beat yourself?…
That’s the question you need to be asking yourself as their Dev Manager all the time. What can they do? What can they do that they are not doing? What can they do if I let them have a run at it? What can they do if I took a step back? What can they do if I left the planning up to them? The goal isn’t to overload your team and gives them MORE…
I don’t think “anyone” wants to rewrite their code (or someone else’s for that matter). But sometimes you have to because whatever it is that is being asked of you cannot scale in what you have built. That’s the Software game, sometimes you need to rebuild it and start from scratch. Housing and construction are often compared to building software with many of the same phrases being interchangeable. The same applies to a house, if…