This is part of a set of four Technical Program Management topologies provided by guest community contributor, Aadil Maan.
About the TPM Hybrid model
Aadil describes this model in his blogpost, "TPM Team Topology - Pt. 1." Below is an excerpt:
"Overview: Similar in structure to the Centralized model however with the exception that certain functional engineering leaders may decide they wish to have their own TPM teams for more tactical purposes.
Operational Mandate: These hybrid models are quite complicated; where as the centralized TPMO’s may own release management at the org level, maintain shared org processes and frameworks (think agile project management), and support the execution of the roadmap at a tactical level by the engineering teams, the secondary TPM teams could operate on a different tactical level in support of the team they report under. Complexity and contention can arise between the central and distributed TPM orgs especially on processes and decision making. This requires a clear understanding of the boundaries of accountability and ownership between the two teams especially when in what matters to defer to which TPM team. Usually, the central TPMO has more power in some scenarios given their close reporting structure to the SVP of Engineering.
Companies Where I Have Seen This: Apple (Pre-iOS and macOS Engineering unification circa pre-2014)."
About this template
Above is a fully interactive template. You can navigate around, drill in and even make changes. If you plan to save changes you make, you'll need to create an account with Functionly. If you already have an account, login to Functionly in a different tab, then come back and refresh this page and choose "duplicate scenario" in the template below.
Who might use this template?
Engineering Leaders, Technical Program Managers, Product Managers, Business Leaders. This is also applicable to anyone interested in the role of TPM.
What's included in this template?
|Job Descriptions||Yes (exportable)|
|Compensation / Salary data||No|