Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 3 · Organization Structures
Organization hierarchies
Lesson 32 of 198 · 12 min
Create an organization hierarchy of the appropriate type, add classified organizations as nodes, build the tree and set the version. Assign the hierarchy to the business unit, selecting the hierarchy type and the classifications it governs. Show which organizations are now available for project ownership and for expenditure in that business unit, then remove an organization from the hierarchy and show it disappear from the list of values. CLASSIFICATION MAKES AN ORGANIZATION ELIGIBLE; THE HIERARCHY MAKES IT AVAILABLE. Both are required, and learners routinely do only one. This is the second-most-common cause of "my organization is not in the list." Hierarchy versions matter for the same reason they do everywhere: reorganizations, and the need to report on last year's structure. Assign the hierarchy at business unit level PER CLASSIFICATION.
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 3 · Organization Structures
- 1What we are building
- 2The decision you cannot undo
- 3The organization object model
- 4The project unit
- 5Owning versus expenditure organizations
- 6Running the structure design workshop
- 7Four worked structures
- 8Business units and the project accounting function
- 9Creating organizations
- 10Classifying organizations
- 11Organization hierarchies
- 12Creating project units
- 13Project unit options
- 14Reference data set assignments
- 15Associating project units with business units
- 16Proving the structure works
- 17What breaks
- 18Lab briefing: Meridian Consulting
- 19Lab solution walkthrough