Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 3 · Organization Structures
What we are building
Lesson 22 of 198 · 1 min
Two business units, project units, a classified organization structure — and a project that creates cleanly, with the right number on it. That is the destination. The dependency chain: BUSINESS UNIT → PROJECT ACCOUNTING FUNCTION → ORGANIZATIONS → CLASSIFICATIONS → HIERARCHIES → PROJECT UNIT → OPTIONS → SET ASSIGNMENTS → ASSOCIATION → FIRST PROJECT. Ten links, and the failure appears at the far end — at project creation, looking like something else. This is the longest module in the phase and the first flagship, because the project unit is the PPM-specific operating entity and almost nobody arrives understanding what it is. The module's argument, in two sentences: the project unit is not the business unit, and the organization that owns a project is not necessarily the one that spends money on it. Those two resolve most of the confusion in this domain. The first seven lessons are design. Sketch, do…
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