Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 3 · Organization Structures
Running the structure design workshop
Lesson 27 of 198 · 2 min
Who is in the room. The finance lead who owns the business unit structure. The PMO lead who owns the project register. And somebody who can speak to how the org chart maps to delivery. WITHOUT THEM, CLASSIFICATION IS GUESSWORK. START WITH THE PROJECT REGISTER, NOT THE ORG CHART. "Show me your current list of projects and how they are numbered." The numbering scheme tells you a great deal — about how many project units you need, and whether the client has thought about it at all. The question sequence. One. How are projects numbered today — and does anyone rely on the number's meaning? Two. Who owns projects — which departments, and is that stable? Three. Whose people work on other departments' projects? Four. Does any project transact in more than one business unit? Five. Do projects cross legal entities? Six. Is there a business reason two groups of…
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