When we own something, it becomes a part of us and we want to see it succeed. It can be something as simple as a bug, a task, or any other kind of ticket. Until it’s in our name though, it’s just a thing that has to be done and anyone on the team can do it. But the moment your name gets added to it, now it’s yours, now it’s something. Now it can…
Too many. Too many lurking around. Too many that I don’t log into but get random texts or emails from. Too many need to be cleaned up. Too many that I don’t even know still exist. Spring cleaning is coming early.
As easy as it would be, Sprint Capacity isn’t all about numbers. The numbers are the foundation to build a capacity but they aren’t the entire story. If you’re being asked to determine your team’s capacity, there are a number of factors you should be considering. Some factors I consider when looking at how I want to manage a sprint and what I think of when determining the capacity of the team; How many stories…
You might be applying for a Junior, Intermediate, Senior Developer job, or maybe a Tech Lead – who knows – but in the back of my head, I’m evaluating you for a job that doesn’t exist yet. When you’re hiring someone you’re presumably doing it because your team is growing. Maybe your role has expanded, your project is growing, your product is doing well in the field, whatever the reason, there is an element of…
We don’t count the least connections. We should because the ones with the least connections are the ones that have the most value. Because we have time to cultivate and grow each one. The more you, the harder it becomes to maintain that same level of touch and value when we had the least of them.