Revising Project Management Processes

Kenneth has 14 years of healthcare experience in government and private industry. Over eight years of experience managing healthcare IT projects, operations, contracts, and personnel. His work experience includes project management, contracts and procurements, data analysis, claims adjudication, business writing, and business process modeling. Kenneth was certified in 2006 as a Project Management Professional.

  Change Management  

Project processes exist to streamline and standardize the work being done by the project team. Whether the process is for scope management, updating schedules or implementing system updates, the process must be understood and followed by everyone on the project team so that the work being done conforms to the expectations and agreements set down for the project.

If the customer has certain expectations for deliverables related to the project, then it is vital for the project manager to make sure those expectations are met. A process describing what needs to be done should be prepared and distributed to everyone involved.

Processes can always be changed, and at times they need to be changed to help the project work. When changes to a process are identified, the project manager will need to examine what needs to be done and approach it carefully so that the changes to the process do not cause additional problems with the project team.

Change is not bad by itself, but if it is not managed well, then it can negatively affect the project. The project manager should follow very careful steps to make changes to existing processes.

Careful Revisions
Knee-jerk reactions are the worst kind of changes that can be made to a project process. Just because one person had an issue or the client just did not like something, there may or may not be a reason to change the …

Please log in or sign up below to read the rest of the article.