Archive for October, 2008
October 30, 2008
What is the Methodology Manager in MPMM Professional?
The Methodology Manager is a software feature which allows you to create, store and share Project Management Methodologies with your peers. Created by Method123 Ltd, the founders of MPMM.com, the Methodology Manager is the first software tool set on the market which allows you to manage multiple project management methodologies at the same time. You can choose to use the project methodology included in MPMM out of the box, and customize it to make it your own. Or you can choose to import your own documentation to create Project Management Methodologies to fit your specific projects. And in the latest multi-user version of MPMM, you can share methodologies with your colleagues.
October 27, 2008
What is a post implementation review and should I have one for my project?
Yes, a post implementation review should always be used for a project that has already completed. After the project has been closed down and the resources have been released a post implementation review is typically undertaken a number of months later to determine weather or not the benefits of the project as specified in the project business case have actually been meet by the customer. Further more a post implementation review will determine weather or not your project was successful and this is based on weather it has meet the objectives which were specified in the project charter. Every project regardless of its size, or type should have a post implementation review completed for it within 2 to 3 months of the project completion.
October 23, 2008
Do I need to always complete a closure report for each of my projects?
Yes, you certainly need to complete the report included in MPMM every time you complete the execution phase of a project. The reason is simply that the report provides management and stake holders as well as the customer with a documented outcome of the status of the project. It helps you to determine weather or not the project completion criteria have been meet and weather there are any out standing items. It also helps you to complete appropriate actions to ensure that your project is closed down quickly and efficiently.
October 20, 2008
Which steps do I take to complete a phase review for the execution of a project ?
The execution phase of a project will be undoubtedly the longest phase of a project life cycle. The reason is that it includes the creation of all of the deliverables for the customer. Therefore the execution phase must have a detailed review at its completion in order to ensure that the project has satisfactorily meet all of the objectives set by the customer before the project can proceed to the following phase which is project closure. When completing a phase review for the execution phase the most important thing is to determine that all deliverables for the project have been 100% completed and that there are no outstanding risks and issues or changes in the associated risk and issues registers. If that is the case then the phase review form can be completed and the project closure phase can be initiated
October 16, 2008
Under what situations should I create a Communications Register for my project?
For small, medium and large projects you should always implement a Communications Register. This register will identify all of the communications events that have taken place for the project and also the communications events that are due to take place in the future. The reason for listing the communications events that are due to take place is that it provides a single place where the project manager can use and control communications to stake holders. For example the register will enable the project manager to view the status of all of the communications to date and determine whether or not the stake holders to the project are being kept in the loop and informed.
October 13, 2008
Should I regularly report on project risk to my stake holders?
Definitely, every time you complete a project status report you should always include a section towards the end which lists all the risks which have been identified in the last reporting period and the likelihood of those risks occurring. If you are able to you should also identify the potential impact on the project, and at a high level list the actions that have been identified to date and for the future to resolve those risks effectively.
Latest data on project management life cycle
October 9, 2008
When I create my Project Status Report should I mention quality at all?
Yes, your Status report should include a schedule which determines whether or not a project is on track and on budget, as well as a determination if the project is resourced.
You will need to list for every deliverable completed in the last reporting period that the quality levels have been meet. Any quality variances should be noted.
October 6, 2008
Other than recording expenses for a project status report what other information should I include?
The project status report includes a determination of whether the project is on schedule or on budget. In addition to that it also determines whether or not the project is adequately resourced. This means that the effort expended at the last reporting period will have to be quantified, effort for the next reporting period should be recorded as well. By doing this you will help the stake holders feel comfortable that there is adequate resource available to build the deliverables agreed with the customer.
