MSAMM
Back to course

Implementing Project Portfolio Management: From Organization Structure to Recognized Revenue · Module 18 · Project Templates and Workflows

The template is the deliverable

Lesson 183 of 198 · 2 min · Free preview

Here is the claim that reframes the whole course. Almost everything you configured in Modules 3 through 17 exists so that a project template can carry it. THE TEMPLATE IS WHAT A PROJECT MANAGER TOUCHES. EVERYTHING ELSE IS PLUMBING. What a template packages. Project type. Plan structure. Planning RBS. Project plan type. Financial plan types. Task structure. Team roles. Classifications. Billing defaults. And more. With a good template, creating a project is: pick the template, name it, set the dates, go. Without one, it is a forty-field form and forty chances to get it wrong. DESIGNED FIRST. BUILT LAST. Designed first, because the template design tells you what configuration you need. Built last, because a template can only assemble what exists. That is why Module 1 told you to design the template on day one even though you build it at the end. It is not a paradox; it is…

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 18 · Project Templates and Workflows

  1. 1The template is the deliverableFree preview
  2. 2Designing the template set
  3. 3Creating a project template
  4. 4Template plan structure and RBS
  5. 5Financial plan types and billing on the template
  6. 6Team, classifications and defaults
  7. 7Approval workflows
  8. 8Profile options and scheduled processes
  9. 9What breaks
  10. 10Lab: four templates, timed, and a runbook