Showing posts with label Planning. Show all posts
Showing posts with label Planning. Show all posts

Monday, 17 February 2014

My PDU Plan

To maintain my PMP qualifications, I need to ensure that I continue to maintain consistent learning with regard to Project Management.  I like the idea that people cannot pass the PMI exams and then forget about keeping up to date with learning and modern practices.

Friday, 14 June 2013

Project Governance

Project governance is the framework which ensures that the project has been correctly conceived and is being executed in accordance with best project management practice and within the wider framework of the internal strategies and processes for each organisation.

Project Governance provides a centralised strategy for project control and reporting, including a set of rules of engagement and guidelines with project teams including external parties.

Tuesday, 11 December 2012

What is in a Project Management Plan

A Project Management Plan (PMP) is an ever evolving document throughout life cycle of the project.  It lays the foundations of the project purpose, scope, structure and actions to complete the required product.  The PMP will start as a shell, containing high level information, but will be completed in more detail as the project progresses.  The estimates, risks, strategies and plans contained in the PMP will become more specific as the information becomes available to the Project Manager.

The PMBoK guide defines the PMP as " the process of documenting the actions necessary to define, prepare, integrate and coordinate all subsidiary plans.  The Project Management Plan defines how the project is executed, monitored and controlled, and closed".

Monday, 12 November 2012

MS Project - My Rules

I get annoyed, quite easily, as you will notice when you read my blog. Something that annoys me is the incorrect use of MS Project. I say incorrect, but I have no official training or expertise in the product, I just know how "I" use it.

I have three simple rules when using MS Project.

Wednesday, 22 February 2012

What is a PID

A PID is a Project Initiation Document and is created once the authorisation to initiate a project has been given.  The PID is the final result of the initiation phase of the project and describes the "what, why, who, how, where, when and how much" of the project.  This document is fairly extensive within the Prince2 Project Management Model and will incorporate many documents, such as the project brief, project scope, project definition and project plan as well as the strategy for the project in terms of communication, quality, configuration management, risk and issues.  More information on these individual topics can be found in the Prince2 book, so I will not go into detail here. 

It is the project managers role to produce the PID and pass it on to the project board for authorisation.  In reality the stakeholders, users and business analysts will need to be involved in producing much of the documentation. 

The PID is a constantly evolving document and remains important throughout the project life cycle.  The PID contains many documents/sections including the project plan, exception plans, risks/issues and therefore is updated throughout the project.  It remains a reference point to who is doing "what, when, how, why". 

Spend time keeping the PID updated and authorised.