I'm looking to learn from people who have had success repeatedly building cross-organizational project teams focused on specific outcomes.

For example, a team is tasked with "Grow revenue of product X by Y %" or "Rework our dev env setup to reduce the time to productivity for joiners."

This is in contrast to back-to-back scrum-based sprints where an ongoing set of new tasks are pulled from a backlog and picked up by anyone with bandwidth and knowledge of the issue's subject area.

These teams might be given little other guidance or required process, and the very ideas for these projects may come from ICs in engineering or bizops going about their normal tasks.

I'm curious about the full lifecycle, including the role of leadership support, evaluation of success, the breakup and re-formulation of these teams and what if any project management structures have worked well.

So far, I have not been able to put my hands on much description of this style of program management, though it is teased at in this recent Pragmatic Engineer article. [1]

[1] https://blog.pragmaticengineer.com/project-management-at-big-tech/