Schedule Project Management Processes

Several things can be noted about how this schedule was developed that will help with the development of the project management processes training plan:

– The schedule is coordinated with the training dates set in the project management Processes Publication Schedule.
– Sole-source purchase and risk assessment were pre-existing internal method picked up by the PMO. Training has been done before, so these trainings can be revised and deployed quickly.
– An external vendor is being used to develop the training on MPMM™ processes. The schedule was coordinated with the vendor.
– PMBOK® training is widely available. The PMO has pre-approved vendors, so training is already available.
– The project review process is simple, and will be developed internally. Development is scheduled to begin after other internal classes are up and running. Because this training is only web-based, classroom <a href=>project management template</a>  schedules are not a problem, and the class can be approved quickly.

The Processes Maintenance Schedule

The Processes Maintenance Schedule is used to update, change, and improve project management processes, and the training classes for processes. It can also be used to track changes to the process of providing project management processes. Each PMO Process Expert should maintain his own schedule.

The previous schedules tracked sets of project management software processes. However, for maintenance, each individual process must be tracked, as a single process within a set may change. If a single process, or a few processes within a large set, are changed, then the version number for each process should be updated. To avoid confusion, a system of sub-versions or release dates should be established for process sets. Each time a process or a few processes within a set are updated, the sub-version or release date of the process set should be updated as well.

Here are some of the types of work typically tracked in the Process Maintenance Schedule:
– Minor corrections and improvements to individual project management processes
– Changes to decision rules governing project management processes
– Major revisions to process sets, often driven by external updates (for example, release of a new version of the PMBOK®)
– Changes to training content
– Changes to publicity for process use
– Improvement of availability or ease of use of the web site that makes processes available

Each process expert follows these nine steps to create a project management process maintenance schedule:
1. Make a copy of the Processes Maintenance Schedule Template. Enter the general information at the top left.
2. Receive input from all users, and also check sources for the processes to identify proposed changes.
3. Enter each proposed change on one row. In the first column of the table, name the change.
4. In the Source field, enter the source of the change, including contact information.
5. In the Reason field, enter a short reason for, or benefit of, the change. See below for a sample list of reasons.
6. List the name of the process being changed in the Process column. Enter the current version of the process in the Process Old Version column. Enter the next version of the project management process in the Process New Version column
7. Enter the name of the Process Set in the Process Set column. Put the current version number of the Process Set in the Process Set Old Version column. Put the new version number that will be used when the change is complete in the Process Set New Version column.
8. Enter the dates planned for the completion of each piece of work: drafting the change, approving the change, updating the version, updating the training, and formally making the new version of the project management process set available.
9. Perform the work and track progress by entering the actual date deliverables are completed.

Join our RSS feed

Click here to join our feed and get the latest articles, every day!