3 ms·
> "Also, engineering managers absolutely have endless work to assign to new hires. So given the headcount, they will definitely make use of it." This seems lik
by potatolicious 4y ago
> "Also, engineering managers absolutely have endless work to assign to new hires. So given the headcount, they will definitely make use of it."
This seems like the crux of the problem. Of course engineering managers always want more headcount - I am one and I would be very happy to get more headcount. My backlog is ten miles long and keeps growing.
But I also understand that if I head enough engineers to actually take care of all the things I want, I will have likely overhired, and am chasing increasingly marginal returns on investment. Some things should not make it off the backlog, because honestly the ROI likely isn't worth it.
"Optimal" staffing at the team level is almost certainly not optimal for either the company or the product. A team that doesn't have to constantly drop things because of lack of resources is likely building a lot of stuff that is poorly-justified.
In a healthy company the desire to do everything is tempered by financial reality and sound judgment - it sounds like both got tossed out the airlock at many companies.
- jarjoura 4y agoLOL, this is also very true. I do question how you manage your backlog though, if there are things on it that should never be implemented, maybe you should clean it out? :-p
- verall 4y agoCould make an internal stakeholder unhappy. Much easier just to let it sit in the backlog forever. Sometimes I come back to a very detailed bug report I wrote about something I found in another team's system. It has been fun to see it grow to almost 4 years old now. Although I am not happy it gets pushed back every release, I would certainly be less happy if it was just closed as "this will never be worth it".