There is always that point in any project where it fell over. The hard part is realizing where you were when it fell over and what you could have done differently. The even harder part is wanting to find this point so you can make a difference on your next project (because who wants to revisit old pains)?
When someone leaves your team, there is a window from the point when they announce when they are leaving to when they actually leave. That window is the amount of time you have to get all of the training this person has learned in their time with you and download it to another person. These are the interactions you don’t want to push off and you want to kick off as soon as possible to…
If you’re not on a team, it’s all you, there is no “we”, it’s just you, and that’s fine. But when you’re on a team, no matter what your role, you’re on a team, and that means only the team can and will ever will.
Just when you think you have reached where you want to be, when you have hit all your goals, you realize that this isn’t where you want to be at all. You want to be somewhere further up, you want to change your game and go in a different direction, you might look back down and realize something you skipped over to get here and then decide that where you are isn’t where you need…
I wrote this article on Medium a while back called the “Software Manager Minimum”. At the time, I was writing about the bare minimum you need to be doing as a manager and leader on a software team in order to keep your team moving forward. In this I boiled it down to three questions you should always be asking yourself on a daily basis; What’s the Pulse of the team? How are we doing? …