After listing conventional failed approaches and the guiding principles in the previous parts, this part will bring this short series to a close with a suggested approach to start managing your non-feature work in a healthier manner. This is not the one approach to rule them all and should not be treated so. It’s a […]
In the previous part, we listed common failed approaches for managing non-feature work (i.e., architectural changes, bugs, tech debt). Following up, this article will delve into the principles that should guide tech leadership in coming up with the right way to keep these under control. Principle: Impact First and Product Involvement The failed approaches often […]
A question that occupies many tech executives is the proper time allocation in their teams for tasks that are not trivial feature development. Fixing bugs, handling technical debt, making architectural changes, creating new tooling (which I’ll group under “non-feature work” in this article). These are all vitally important for a growing team to stay productive […]
I’ve found a calling in helping as many companies as possible create world-class engineering teams. That is why the matter of cultivating a culture of professionalism is often on my mind. Some companies have no such problem. They easily hire incredibly talented people all around. Highly motivated people that come equipped with the knowledge of […]
When helping companies rapidly improve their teams, a common issue is understanding why some people are not performing as expected. These are usually great engineers with a solid track record and experience. You and your managers might be trying all sorts of things to motivate them or help them to no avail. And the most […]