This is part of a set of four Technical Program Management topologies provided by guest community contributor, Aadil Maan.
About the TPM Decentralized model
Aadil describes this model in his blogpost, "TPM Team Topology - Pt. 1." Below is an excerpt:
"Overview: TPMs are hired by and report to the functional Engineering Leaders. There is no centralized TPMO. These IC TPMs can eventually grow entire teams of TPMs under them as the functional engineering area grows both in scope and resources.
Operational Mandate: The TPMs are responsible for supporting the engineering teams they report under. There are no shared org processes and frameworks (think agile project management) as every team can decide their own processes (unless the TPMs self organize into a unofficial pseudo TPMO), and support the execution of the roadmap at a tactical level for the engineering team they support.
Companies Where I Have Seen This: Blackberry (Post QNX Acquisition), Google (various teams)."
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?
| Org structure | Yes |
| Roles | Yes |
| Accountabilities | No |
| Responsibilities | Yes |
| Job Descriptions | Yes (exportable) |
| Compensation / Salary data | No |
