We’ll see more initiatives organized end-to-end by small groups of smart people, with virtual teams/coalitions forming to bypass “archaic” processes and deliver meaningful results.
What you’re describing here has always been the case. The pattern in software is always that a small, actually empowered group does the initial development and r&d, then if the product is a success the maintenance people come in and drain it of any progress via overbearing process and middle management. There’s rare exceptions, but I’ve seen this over and over again.
Small teams build good things, then they get acquired and those things are slowly or quickly destroyed.
In many cases, yes. A difference now will be the long-term size and composition of the teams (smaller & more generalists, with PMs, POs & Architects just as likely to contribute code as engineers)
2 pizza teams can become 1 pizza teams who can manage an entire product/component, or more. And those 3+ pizza teams can strip the fat or split into more productive teams.
I think we’ll also see increased demand for platform/deployment standardization and concentrated/novel support structures, as teams start biting off more than they can chew, along the the desire for out-of-the-box guardrails around AI code & tools.
Maybe? If corporate structures made sense then sure, but they haven’t made sense my entire time in the industry and I doubt they’ll start making sense because of this.
What you’re describing here has always been the case. The pattern in software is always that a small, actually empowered group does the initial development and r&d, then if the product is a success the maintenance people come in and drain it of any progress via overbearing process and middle management. There’s rare exceptions, but I’ve seen this over and over again.
Small teams build good things, then they get acquired and those things are slowly or quickly destroyed.
In many cases, yes. A difference now will be the long-term size and composition of the teams (smaller & more generalists, with PMs, POs & Architects just as likely to contribute code as engineers)
2 pizza teams can become 1 pizza teams who can manage an entire product/component, or more. And those 3+ pizza teams can strip the fat or split into more productive teams.
I think we’ll also see increased demand for platform/deployment standardization and concentrated/novel support structures, as teams start biting off more than they can chew, along the the desire for out-of-the-box guardrails around AI code & tools.
Maybe? If corporate structures made sense then sure, but they haven’t made sense my entire time in the industry and I doubt they’ll start making sense because of this.