"the folks that make magic happen and are actually developing code. Although I also tend to think, now since my role has expanded outside of just looking at product and engineering, into the whole thing that makes magic happen from a delivery standpoint. But yes, utilization is one of those words that's coming up so much right now, too, as we start to think about AI and how that rolls into organizations."
"Initially, was looking specifically at our product and engineering function, but then expanded my role out. And then, Shane, I know we go way back, but our first meeting, even further back, was when I was running product at Rally Software and then I had a short stint in the DevOps space, specifically at GitLab, and now find myself at Tempo for the last four years, which has been a blast."
Utilization provides a narrow, mechanical view of engineering work and can reduce talented developers to cogs. High utilization is often pursued but reflects busyness rather than effective software delivery. Capacity planning should account for the broader delivery system beyond individual product and engineering roles. Leadership roles that span product, engineering, and go-to-market help align measures with outcomes. The emergence of AI is intensifying attention on how teams are utilized and how capacity is measured. Engineers represent a high-cost, high-talent investment; misapplying utilization risks burnout and suboptimal outcomes.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]