Susanne Madsen - Developing Project Leaders
  • Home
  • Services
    • Workshops
    • Speaking
    • Coaching
    • Stress management
    • Testimonials
  • Bio
  • Books
  • Blog
  • Resources
  • Videos
  • Contact
  • Library

What makes a perfect Project Initiation Document (PID)?

7/4/2014

9 Comments

 
The Project Initiation Document (PID) – or the Definition Document – is one of the most important artifacts in project management because it provides a foundation for the project. It specifies why the project is important, what will be delivered, when it will be delivered and how. It’s the contract between the project management team and the steering committee – or sponsor – if you like.
Picture
Unfortunately many project managers don’t take the time to write a proper PID. They write a document which is far too generic and therefore doesn’t bear any real meaning. The purpose of writing a PID is not to tick a box so that you can say you have done it, but to ensure that everybody understands the premise of the project. A good PID should answer the following questions:

Why are we undertaking the project? It’s important to understand the background of the project, the motivation for undertaking it and it’s objectives. A good project manager is not only interested in delivering an output or a capability to their customer, but interested in the wider context and the benefits that this capability will ultimately bring about.

What are we delivering? A good PID is as specific as possible about what is in scope and what is out of scope of the project, and it makes use of flow diagrams and Product Breakdown Structures to visually illustrate the boundaries. It also clarifies the project’s success criteria, i.e. everything that must be fulfilled in order for the project to be considered a success.

Who is responsible? It’s important to clarify who plays which roles on the project so that nothing falls through the cracks. Specify who takes the role of project manager, team leader, sponsor, supplier and user representative. You should also document who the main stakeholders are and who the steering committee comprises of.

How will the project be delivered? When you kick off a project you have to determine which approach you will use. Will you use a waterfall or an agile methodology? How will you communicate with the stakeholders? How will you test the quality of the products or services you are delivering and how will you keep on top of risks, issues and changes to scope?

When will the project be delivered? Unless you use a very structured waterfall methodology, you are unlikely to have an in depth schedule of what will happen when. For the PID it will suffice to include a milestone plan which highlights the main phases and activities of the project. As most people are visually minded it is a benefit if you also include a visual roadmap. The more graphical you can make the PID the better.

What are the risks, issues and constraints? Projects often derail because of unforeseen risks, so make sure you get them out in the open as early as possible. Include a snapshot of the project’s top 10 risks and issues and assign owners and mitigating actions. Also remember that constraints and dependencies often turn out to be risks.  

How much is it likely to cost? It is good practice to include a cost estimate in the PID along with any budgetary constraints. Provide the assumptions your team used when they came up with the estimate as well as details about how often you will review the estimates.

When it comes to completing the PID, make sure that you don’t do it in isolation, but that you involve the team as much as possible. After all, it’s the team that will do most of the work. Write the document in plain English and avoid project management speak. Jargon alienates your readers.

And one final point. When you’ve written the PID, don’t just send it out via email and expect your stakeholders to read it. Set up walk-through sessions where you take them through a PowerPoint version of the PID highlighting the main points. 

You can download a PID (or PDD) template for free from the resources page.


If you liked this post, you may also like:
Initiating and Planning Your Project, Part I
Risk management is how adults manage projects!
8 Tips for Managing Project Costs 

Top Tips for Gathering Requirements

9 Comments
Aamer Inam
10/4/2014 02:25:32

Also including the required hardware , software resources along with training requirements of the teams involved can add a lot of value . very nice article indeed.

Reply
VJBaskar link
6/4/2017 11:51:40

Nice explanation, It reminds me to remember things I know in Project Management, but tend to forget during my busy day! Thanks! Constraints are used to impose logic on activities that may not be realistically scheduled with logic links, Two constraints are permitted against each activity. They are titled Primary and Secondary Constraint. After the Primary has been set, a Secondary may be set only when the combination is logical and therefore a reduced list of constraints is available from the Secondary Constraint list after the Primary has been set.

Reply
Vikram Razdan
24/6/2017 20:02:15

The PID is essentially a detailed project proposal to obtain 'budgetary/financial' approval from Project sponsors, who in turn appoint the Steering committee to oversee the project implementation.

Reply
S Chapman
21/12/2017 16:16:30

No not really. A PID is essentially shared with all project members. New members are given a copy with their name included under appripriate role.

Reply
naureen Kabaso
9/1/2018 06:56:14

PID is the very important document that guides, directs, coordinates and model incase no understanding it brings the project into direction and shape, mainly reference is also done or either consulting to the
steering members and ideals flows with openness of meetings with the objective on the table.

Reply
madhu link
3/8/2019 09:00:25

I wondered upon your blog and wanted to say that I have really enjoyed reading your blog posts. Any way I’ll be subscribing to your feed and I hope you post again soon.

Reply
aruna ram link
5/8/2019 12:01:33

The article is so informative. This is more useful for me. Keep doing great work and a good job.

Reply
Raneedevan link
7/8/2019 06:39:05

valuable blog...thanks for sharing...

Reply
Salesforce Training in Chennai link
8/8/2019 08:04:20

I really admired your post, such great and useful information that you have mentioned here.

Reply

Your comment will be posted after it is approved.


Leave a Reply.

    Categories

    All
    Agile
    Authenticity
    Building Relationships
    Coaching
    Delegation
    Estimation
    Feedback
    Handling Conflict
    Innovation
    Iron Triangle
    Limiting Factor
    My Story
    Perception Of Failure
    Podcasts
    Positive Attitude
    Proactive Project Management
    Progress Reporting
    Project Costs
    Project Failure
    Project Initiation
    Project Leadership
    Project Management Mistakes
    Recruitment
    Requirements
    Resistance To Change
    Risk Management
    Self Esteem
    Stakeholder Management
    Stress Management
    Team Motivation
    Time Management
    Trust
    Vision And Mission

    Picture

    Susanne Madsen

    Susanne is a project leadership coach and the author of The Power of Project Leadership (now in 2nd edition). Read more..

    Picture

    Download FREE PM RESOURCES

    Picture
    Picture
    Picture
    Picture
    Picture

    Archives

    November 2020
    September 2020
    June 2020
    March 2020
    February 2020
    January 2020
    December 2019
    October 2019
    June 2019
    May 2019
    March 2019
    February 2019
    December 2018
    November 2018
    October 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    January 2014
    December 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012
    September 2012
    August 2012
    July 2012
    June 2012
    May 2012
    April 2012
    March 2012
    February 2012
    January 2012
    December 2011
    November 2011
    October 2011
    September 2011
    August 2011
    July 2011
    June 2011
    May 2011
    April 2011
    February 2011

    View my profile on LinkedIn

    RSS Feed

Developing Project Leaders