Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 8 · Resource Breakdown Structures
Centralized versus project-level maintenance
Lesson 86 of 198 · 12 min
A planning structure can be centrally controlled — only administrators change it — or allow project managers to add resources at project level. Centralized: consistent, reportable, and slow to respond when a project needs something new. Project-level: flexible, responsive, and produces a long tail of one-off resources that break portfolio reporting. The recommendation. Centralized for the reporting structure, without exception. For the planning structure, centralized by default with a defined, FAST process for adding resources on request. If the process is slow, project managers will work around it and the data suffers. Then: show the setting, add a resource centrally, enable project-level addition and add one from within a project, and show the difference in the resulting structure. THIS IS A GOVERNANCE DECISION DISGUISED AS A CHECKBOX. Whichever you choose, somebody owns the structure and somebody answers requests. NAME THEM — the lab requires a named process and owner, not…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue, with a certificate on completion and a fourteen-day refund window.
In this module: Module 8 · Resource Breakdown Structures
- 1What we are building
- 2Why the RBS is permanent
- 3Resource classes and resource formats
- 4Planning versus reporting structures
- 5Designing the hierarchyFree preview
- 6Running the RBS design workshop
- 7Creating a planning RBS
- 8Adding planning resources
- 9Centralized versus project-level maintenance
- 10Creating a reporting RBS
- 11Proving the structure works
- 12What breaksFree preview
- 13Lab briefing: plan for a CFO and a bid team at once
- 14Lab solution walkthrough