Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 8 · Resource Breakdown Structures
Designing the hierarchy
Lesson 82 of 198 · 2 min · Free preview
The mistake: modelling the org chart, or the expenditure type list, or both, into a five-level hierarchy with several hundred nodes. Now a project manager scrolls through hundreds of entries to plan four lines. Two constraints, and they pull apart. Reporting wants depth. More levels means more analysis. Planning wants brevity. Fewer, clearer entries means better plans. The resolution: planning structure shallow and usable; reporting structure deeper, with the mapping doing the work. PLANNING RARELY NEEDS MORE THAN TWO OR THREE LEVELS. REPORTING RARELY MORE THAN FOUR. If you are deeper, ask which report needs the fifth level and who reads it. The design method. Start with the executive's questions. Each one is a reporting level or a dimension. Then ask what a project manager needs to select when planning. That is the planning structure. Then check every planning resource maps to a reporting node. THE USABILITY TEST — SHOW…
This lesson is free
Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.
Watch the full lessonIn 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