Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 18 · Project Templates and Workflows
Designing the template set
Lesson 184 of 198 · 2 min
ONE TEMPLATE PER GENUINELY DIFFERENT WAY OF STARTING A PROJECT. Fewer than the number of project types. Far fewer than the number of service lines. What justifies a separate template. A different project type. A materially different default task structure. Different financial plan types. Different billing setup. What does not: a different practice, a different client, a different region. Those are classifications set at creation — third time this course has given that answer, and the repetition is deliberate. A typical set: T&M engagement, fixed-price engagement, internal initiative, capital project, bid. Three to six templates. The task structure question, and it has a failure at each end. How much of the work breakdown should the template pre-populate? Too little and every project manager builds from scratch, inconsistently. Too much and they spend their first hour deleting tasks that do not apply. The sweet spot is a standard top level with…
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