Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 3 · Organization Structures
Creating project units
Lesson 33 of 198 · 13 min
Create a project unit: name, description. Set the project numbering method and format. Set the default calendar behaviour — noting the forward dependency to Module 4. Save. Create a second project unit to demonstrate the pattern — then discuss whether the Meridian scenario actually needs it. PROJECT NUMBERING IS SET HERE AND IS EFFECTIVELY PERMANENT. Automatic sequence or manual entry — and if manual, the convention is a governance problem rather than a system one. If adopting legacy numbers, manual numbering is usually the answer — and uniqueness becomes your responsibility during migration. The second unit is created on camera and then argued against. Seeing a design decision reversed with reasoning is worth more than seeing one made — it is the only place in the course where somebody changes their mind on screen.
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