Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 18 · Project Templates and Workflows
What breaks
Lesson 191 of 198 · 2 min
Seven cases. One. "Every project is configured differently." No templates — or templates nobody uses. Two. "The templates are out of date." No owner. Configuration changed; templates did not. Three. "Creating a project takes twenty minutes." The template is incomplete. Everything not on it is a manual step. Four. "Approvals stall." No escalation or delegation. Five. "The dashboard is stale, invoices did not generate, and revenue is missing." Three symptoms, one cause: scheduled processes not scheduled. One root cause, several symptoms — and recognizing that is the diagnostic skill. Three teams report three unrelated faults on the same morning. They are one thing. Six. "Nobody knows why this profile option was changed." An undocumented change. Seven. "A project was created without a classification and cannot be reported on." The classification was not mandatory on the template. THE LAST MODULE'S FAILURES ARE MOSTLY ORGANIZATIONAL RATHER THAN TECHNICAL. That is appropriate. By…
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 18 · Project Templates and Workflows
- 1The template is the deliverableFree preview
- 2Designing the template set
- 3Creating a project template
- 4Template plan structure and RBS
- 5Financial plan types and billing on the template
- 6Team, classifications and defaults
- 7Approval workflows
- 8Profile options and scheduled processes
- 9What breaks
- 10Lab: four templates, timed, and a runbook