Projects are forgiving at the beginning or the end - never both.
— Unattributed

Synchronizing teamwork into a formal project is incredibly valuable, saving time, frustration, and relationships on countless occasions. Synchronizing helps to minimize surprises, plan non-project activities, and get the best planning ideas on paper so that they become reality. A piece of good news for innovation teams: all project plans should have the same starting point. There is no need to reinvent the wheel.

The sections below paint a picture of a healthy project plan, captured in a tool meant for a project plan (like Microsoft Project), not in a tool meant for equations (like Microsoft Excel):

  1. Inventory every asset that is in scope

  2. Start your project plan with the parents People, Process, and Technology

  3. For People, add children of ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement)

  4. For Process, add children of Current State (CS) and Future State (FS)

  5. For Technology, add children to suit your choice of Agile or Waterfall; e.g. Design, Build, Test, Deploy (DBTD)

  6. Add each asset as children of ADKAR, CS, FS, or DBTD

  7. Add the Five Verbs as children to every asset (Draft, Review, Revise, Approve, Distribute)

  8. Add dependencies as you see them

  9. Add resource assignments

  10. Consult the resources for their duration estimates

projectplan.png

Unique traits of every project are within each asset; e.g. within the project charter, within the process flow, within training materials. If this feels oversimplified or incomplete to you, here are three cautions:

  1. Meetings go in your scheduling tool (like Microsoft Outlook); it’s a slippery slope and an impossible task to think you can centrally manage and monitor all the meetings your project will have

  2. a task list is a sign that you are reinventing the wheel, you are micromanaging, and you are losing sight of the big picture of the project

  3. You have verb sprawl; using thirty verbs to manage your project is going to be a problem … you really only need Five Verbs

A robust, disciplined project plan is instrumental to minimizing waste and keeping an ensemble’s focus exactly where it needs to be, such as updating Percent Complete on a weekly basis!


Upstream Assets: Project Charter, Workload Report, Stoplight Report

Downstream Assets: numerous project-specific assets

Previous
Previous

Why You Are A Factory

Next
Next

Object Model